I quit the browser, and one of my bookmark timers seems to have gone off during the shutdown process: NTDLL! 77f7629c() nsDebug::Assertion(const char * 0x016d4c4c, const char * 0x016d4c38, const char * 0x016d4c0c, int 0x000001bd) line 186 + 13 bytes RDFContainerImpl::Init() line 445 + 39 bytes NS_NewRDFContainer(nsIRDFContainer * * 0x0012e558) line 501 + 8 bytes CreateNewRDFContainer(nsISupports * 0x00000000, const nsID & {...}, void * * 0x0012e7c8) line 99 + 53 bytes nsGenericFactory::CreateInstance(nsGenericFactory * const 0x01ae4710, nsISupports * 0x00000000, const nsID & {...}, void * * 0x0012e7c8) line 43 nsComponentManagerImpl::CreateInstance(nsComponentManagerImpl * const 0x00bf5c20, const nsID & {...}, nsISupports * 0x00000000, const nsID & {...}, void * * 0x0012e7c8) line 1246 + 24 bytes nsComponentManager::CreateInstance(const nsID & {...}, nsISupports * 0x00000000, const nsID & {...}, void * * 0x0012e7c8) line 82 nsBookmarksService::WriteBookmarksContainer(nsIRDFDataSource * 0x023db600, nsOutputFileStream {...}, nsIRDFResource * 0x023dadb0, int 0x00000000) line 3853 + 49 bytes nsBookmarksService::WriteBookmarks(nsIRDFDataSource * 0x023db600, nsIRDFResource * 0x023dadb0) line 3833 + 35 bytes nsBookmarksService::Flush(nsBookmarksService * const 0x023d9638) line 3498 + 25 bytes nsBookmarksService::FireTimer(nsITimer * 0x02115f40, void * 0x023d9630) line 2060 TimerImpl::Fire(unsigned long 0x5275b69c) line 312 + 17 bytes TimerImpl::ProcessTimeouts(unsigned long 0x5275b69c) line 191 FireTimeout(HWND__ * 0x00000000, unsigned int 0x00000113, unsigned int 0x000049a8, unsigned long 0x5275b69c) line 105 + 9 bytes USER32! 77e7185c() USER32! 77e89050() USER32! 77e8ad30() USER32! 77e8b044() USER32! 77e8aed8() USER32! 77e8b203() USER32! 77e8a5a6() nsDebug::Assertion(const char * 0x02a274b8, const char * 0x02a27490, const char * 0x02a2745c, int 0x00000038) line 169 + 22 bytes nsDebug::WarnIfFalse(const char * 0x02a274b8, const char * 0x02a27490, const char * 0x02a2745c, int 0x00000038) line 242 + 21 bytes nsMemCache::~nsMemCache() line 56 + 54 bytes nsMemCache::`scalar deleting destructor'(unsigned int 0x00000001) + 15 bytes nsMemCache::Release(nsMemCache * const 0x028df5a0) line 69 + 131 bytes nsCOMPtr<nsINetDataCache>::~nsCOMPtr<nsINetDataCache>() line 434 nsCacheManager::~nsCacheManager() line 67 + 33 bytes nsCacheManager::`scalar deleting destructor'(unsigned int 0x00000001) + 15 bytes nsCacheManager::Release(nsCacheManager * const 0x028df950) line 49 + 131 bytes DeleteEntry(nsHashKey * 0x023b84a0, void * 0x028cf030, void * 0x00000000) line 210 + 18 bytes _hashEnumerateRemove(PLHashEntry * 0x023b8460, int 0x00000037, void * 0x0012fdbc) line 227 + 26 bytes PL_HashTableEnumerateEntries(PLHashTable * 0x00bf5fd0, int (PLHashEntry *, int, void *)* 0x1001bba0 _hashEnumerateRemove(PLHashEntry *, int, void *), void * 0x0012fdbc) line 368 + 15 bytes nsHashtable::Reset(int (nsHashKey *, void *, void *)* 0x10048340 DeleteEntry(nsHashKey *, void *, void *), void * 0x00000000) line 243 + 20 bytes nsObjectHashtable::Reset() line 344 nsObjectHashtable::~nsObjectHashtable() line 310 nsObjectHashtable::`scalar deleting destructor'(unsigned int 0x00000001) + 15 bytes nsServiceManagerImpl::~nsServiceManagerImpl() line 235 + 31 bytes nsServiceManagerImpl::`scalar deleting destructor'(unsigned int 0x00000001) + 15 bytes nsServiceManagerImpl::Release(nsServiceManagerImpl * const 0x00bf4080) line 244 + 132 bytes nsServiceManager::ShutdownGlobalServiceManager(nsIServiceManager * * 0x00000000) line 484 + 17 bytes NS_ShutdownXPCOM(nsIServiceManager * 0x00000000) line 537 + 7 bytes main(int 0x00000001, char * * 0x00bf45e0) line 721 + 8 bytes mainCRTStartup() line 338 + 17 bytes Looks like timers need to be shut off cleanly before xpcom starts to shut down.

m15, m14 if this is a repeatable problem.

Adding "crash" keyword to all known open crasher bugs.

Steve, does this even happen anymore?

Putting on need info radar.

I haven't seen this.

I haven't ever seen this(of course it's hard to 'see'). This will be closed as wfm the next time it pops up.

Just because no one is seeing this on a regular basis doesn't mean it's fixed. It's very timing dependent. What needs to happen is proper shutdown/synchronization code for the timer service.

[nsbeta2-] if renominating, please supply Talkback stats showing how bad this is.

Pavlov said he's going to fix this!!!

Move to M20 target milestone.

Nav triage team: [nsbeta3-]

Adding nsbeta3 keyword to bugs which already have nsbeta3 status markings so the queries don't get all screwed up.

Reassigning 79 Bookmarks bugs to Ben. I was told this was going to be done shortly about two months ago, but it clearly hasn't been. I think that's long enough for all these bugs to remain assigned to nobody. Feel free to filter all this spam into the trashcan by looking for this string in the message body: ducksgoquack

Looks like a dup. bug 59530 has a patch that fixes this. *** This bug has been marked as a duplicate of 59530 ***

I cant prove it's a dupe - but I'm reasonably certain VERIFIED Dupe