cvs build from sunday afternoon w/ lots of patches but none near netwerk. this has happened to me twice (which is a lot given that i rarely try quiting and usually crash instead). ###!!! ASSERTION: Should have thread when shutting down.: 'Not Reached', file i:/build/mozilla/netwerk/base/src/nsSocketTransportService.cpp, line 763 Break: at file i:/build/mozilla/netwerk/base/src/nsSocketTransportService.cpp, line 763 nsDebug::Assertion(const char * 0x03d3e494, const char * 0x10137ba4, const char * 0x03d3e454, int 763) line 280 + 13 bytes nsDebug::NotReached(const char * 0x03d3e494, const char * 0x03d3e454, int 763) line 457 + 22 bytes nsSocketTransportService::Shutdown(nsSocketTransportService * const 0x01085540) line 763 + 21 bytes nsIOService::SetOffline(nsIOService * const 0x01084da8, int 1) line 588 + 26 bytes nsIOService::Observe(nsIOService * const 0x01084dac, nsISupports * 0x002ddba4, const char * 0x10115244, const unsigned short * 0x00000000) line 754 nsObserverService::NotifyObservers(nsObserverService * const 0x01033308, nsISupports * 0x002ddba4, const char * 0x10115244, const unsigned short * 0x00000000) line 213 NS_ShutdownXPCOM(nsIServiceManager * 0x00000000) line 701 main(int 3, char * * 0x002e44c0) line 1913 + 8 bytes mainCRTStartup() line 338 + 17 bytes - this 0x01085540 |+ nsISocketTransportService {...} |+ nsIRunnable {...} |+ mRefCnt {...} |+ _mOwningThread {...} | mAutodialEnabled 1 |+ ops {...} |+ mThread 0x00000000 |+ mThreadEvent 0x01087080 | mThreadLock 0x01087f10 | mThreadRunning 0 |- mWorkQ {...} ||+ next 0x01085564 |\+ prev 0x01085564 | mConnectedTransports -8 | mTotalTransports 0 | mSelectFDSetCount 1 |+ mSelectFDSet 0x0108d4a8 |- mActiveTransportList 0x03e086b0 |\+ 0x00000000 |+ mStringBundle {...} |- mDNSService {...} |\+ mRawPtr 0x01070ef8 |- mEventQService {...} |\+ mRawPtr 0x00fa8088 \+ mHostDB {...}

I get this assertion every time I close my debug build. Kind of annoying...

+clean-report

bug 176919 will eliminate this assertion; however, the problem may still exist.

to socket owner.

i believe this should be FIXED with the patch from bug 176919. i don't think this has anything to do with the global thread manager. that is timers specific.