This is a topcrasher for Netscape 7.01. I was going to reopen bug 146466, but noticed that this crash was only happening on Windows 95 and 98. Still, that bug might be helpful since the stack is almost identical. This is only happening on the Gecko 1.0 Branch (Netscape 7.01). Here is the latest from Talkback: 10 nsWindowMediator::RemoveAndUpdateSynthetics 44 Source File : http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/xpfe/appshell/src/nsWindowMediator.cpp line : 1492 ==================================================================================================== Count Offset Real Signature [ 42 nsWindowMediator::RemoveAndUpdateSynthetics fe6db4ed - nsWindowMediator::RemoveAndUpdateSynthetics ] [ 1 nsWindowMediator::RemoveAndUpdateSynthetics 32815978 - nsWindowMediator::RemoveAndUpdateSynthetics ] Crash date range: 2002-12-11 to 2002-12-16 Min/Max Seconds since last crash: 4 - 150913 Min/Max Runtime: 4 - 150913 Keyword List : Count Platform List 15 Windows 98 4.10 build 67766446 14 Windows 98 4.90 build 73010104 8 Windows 98 4.10 build 67766222 3 Windows NT 5.1 build 2600 2 Windows 95 4.0 build 67109975 1 Windows NT 4.0 build 1381 Count Build Id List 43 2002112016 No of Unique Users 39 Stack trace(Frame) nsWindowMediator::RemoveAndUpdateSynthetics [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWindowMediator.cpp line 1492] nsWindowMediator::UnregisterWindow [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWindowMediator.cpp line 292] nsWindowMediator::~nsWindowMediator [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWindowMediator.cpp line 212] nsWindowMediator::`scalar deleting destructor' nsWindowMediator::Release [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWindowMediator.cpp line 873] nsSupportsArray::Clear [d:\builds\seamonkey\mozilla\xpcom\ds\nsSupportsArray.cpp line 601] nsSupportsArray::DeleteArray [d:\builds\seamonkey\mozilla\xpcom\ds\nsSupportsArray.cpp line 304] nsSupportsArray::`vector deleting destructor' nsCOMPtr_base::~nsCOMPtr_base [d:\builds\seamonkey\mozilla\xpcom\glue\nsCOMPtr.cpp line 65] InMemoryDataSource::~InMemoryDataSource [d:\builds\seamonkey\mozilla\rdf\base\src\nsInMemoryDataSource.cpp line 979] InMemoryDataSource::`scalar deleting destructor' InMemoryDataSource::Internal::Release [d:\builds\seamonkey\mozilla\rdf\base\src\nsInMemoryDataSource.cpp line 983] InMemoryDataSource::Release [d:\builds\seamonkey\mozilla\rdf\base\src\nsInMemoryDataSource.cpp line 979] nsWindowMediator::Release [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsWindowMediator.cpp line 867] nsCOMPtr_base::assign_with_AddRef [d:\builds\seamonkey\mozilla\xpcom\glue\nsCOMPtr.cpp line 74] PL_DHashTableEnumerate [d:\builds\seamonkey\mozilla\xpcom\ds\pldhash.c line 602] 0x550004c2 (15140544) Comments: reinstalling version 7 - which failed with an error message (15140503) Comments: just turning on computer (15138711) Comments: Went to bed and had to shut down comuter on line (15130194) Comments: URL Filter Configuration is denied. What can i do? (15114665) Comments: playing a game and screen changed color all is red Cc'ing a few people from the other bug.
Please correct the component if I got it wrong, I just went by what was set in bug 146466. Also cc'ing rjc since he was the owner of that bug.
All this code was chopped out in the trunk for bug 132175. Reassigning to rjc for ideas.
Assignee: adamlock → rjc
This is only crashing Win95/98 on the Gecko1.0 branch...and since the code has been chopped off the Trunk, I'm making this topcrash-. Chances of this being fixed on the branch are probably really low...so also marking this worksforme. If we decide to revisit this problem on the Gecko1.0 branch, feel free to reopen.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Keywords: topcrash → topcrash-
Resolution: --- → WORKSFORME
reopening to mark wontfix, so we don't assume this is actually fixed!
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Status: REOPENED → RESOLVED
Last Resolved: 15 years ago → 15 years ago
Resolution: --- → WONTFIX
Crash Signature: [@ nsWindowMediator::RemoveAndUpdateSynthetics]
You need to log in before you can comment on or make changes to this bug.