On Wed, 2009-10-21 at 12:55 -0400, Steve Huston wrote: > Hi Andrew, > ... > > > > If I run the broker and then run perftest against it perftest > appears > > hang waiting for the connection to start > > There is an intermittent (for some it's always, for some it's never) > hang similar to what you describe. I've not been able to reproduce it. >
It isn't intermittent for me it occurs in all the builds I've tried. > Can you run anything else? Python_tests, maybe? > Is the known issue on the broker or client sides? I can test Linux against windows easily enough to see which side(s) my problem is on. > ... > This is "normal" - I tracked it once to a different behavior between > Microsoft and gcc STL iterators or something similar. I think that this really needs to be resolved ASAP the unit_test program is our initial "QA" for a checkin without it passing it's pretty easy to add in regressions. Certainly the low levels of the Windows port is sufficiently different to expect there to be different failure modes. > > > ..\..\..\qpid\cpp\src\tests\ClientSessionTest.cpp(252): last > > checkpoint > > ************* > > *** 5 failures detected in test suite "Master Test Suite" > > Detected memory leaks! > > ... and a long list of leaked blocks... > > Yes, once it crashes there are leaks galore. They will be looked at > when unit_test doesn't crash. I'd expect it to leak is it crashes. But the crashing is a problem. The Linux experience is that the leaks pretty much go away if you run to completion. Andrew --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
