this is a tricky crash to reproduce...but i managed to get it to occur about four times on my Mac today [using 2001.07.02.03-branch comm bits]. unsure what the proper component should be, so trying toolkit initially... 1. go to http://faqs.org 2. in the left-hand frame, bring up the context menu over the "NO FRAMES" linked image. use either command+click or the long click to bring up the context menu. 3. select Properties from the menu, and the Properties dialog will appear. 4. option+click [i know that's weird, but i found this while fumbling w/the keyboard ;)] either the first or second links. 5. if you don't crash, repeat 1-4 until you do. here's a trace from talkback #32446111: 0xffc10000 ViewportFrame::Destroy() [nsViewportFrame.cpp, line 141] FrameManager::Destroy() [nsFrameManager.cpp, line 456] PresShell::~PresShell() [nsPresShell.cpp, line 1490] PresShell::Release() [nsPresShell.cpp, line 1374] nsCOMPtr_base::~nsCOMPtr_base() [nsCOMPtr.cpp, line 49] GlobalWindowImpl::Focus() [nsGlobalWindow.cpp, line 1771] nsEventStateManager::PreHandleEvent() [nsEventStateManager.cpp, line 592] will attach Macsbug report soon.

if someone could find a simpler test case for this, that'd be great! i know this is a difficult one to replicate...

Macsbug trace: Calling chain using A6/R1 links Back chain ISA Caller 00000000 PPC 04C917C0 068B5E00 PPC 04C81C0C 068B5DA0 PPC 04C81258 068B5A70 PPC 069D7700 NSGetModule+0181C 068B5A30 PPC 04BE805C nsMacMessageSink::IsRaptorWindow(GrafPort*)+0141C 068B59E0 PPC 04BE86D4 nsMacMessageSink::IsRaptorWindow(GrafPort*)+01A94 068B5990 PPC 04BE8BC8 nsMacMessageSink::IsRaptorWindow(GrafPort*)+01F88 068B5940 PPC 04BE9804 nsMacMessageSink::IsRaptorWindow(GrafPort*)+02BC4 068B58F0 PPC 04BE98E4 nsMacMessageSink::IsRaptorWindow(GrafPort*)+02CA4 068B58A0 PPC 04BE6A90 nsMacMessageSink::DispatchOSEvent(EventRecord&, GrafPort*)+00038 068B5860 PPC 04BE2948 NSGetFactory+06F64 068B5820 PPC 04BE3394 NSGetFactory+079B0 068B57D0 PPC 04BE4238 NSGetFactory+08854 068B5780 PPC 04BE3034 NSGetFactory+07650 068B5730 PPC 04BE2E2C NSGetFactory+07448 068B56B0 PPC 04BD86BC 068B5670 PPC 04BD8634 068B5620 PPC 04580A90 NSGetModule+0009C 068B55D0 PPC 0458E79C NSGetModule+0DDA8 068B54A0 PPC 045813E0 NSGetModule+009EC 068B5400 PPC 045BA134 NS_NewPresShell(nsIPresShell**)+0B268 068B5390 PPC 045BA2B4 NS_NewPresShell(nsIPresShell**)+0B3E8 068B5330 PPC 047D1B20 NS_NewHTMLCSSStyleSheet(nsIHTMLCSSStyleSheet**)+ 0C5C8 068B4D20 PPC 04B06740 nsGetInterface::~nsGetInterface()+03E24 068B4C50 PPC 06ACA1AC nsCOMPtr_base::~nsCOMPtr_base()+00030 068B4C10 PPC 045AF460 NS_NewPresShell(nsIPresShell**)+00594 068B4BD0 PPC 045AFB18 NS_NewPresShell(nsIPresShell**)+00C4C 068B4B10 PPC 0468A4D0 NS_NewFrameManager(nsIFrameManager**)+005D8 068B4AA0 PPC 04645140 NS_NewPrintContext(nsIPrintContext**)+16598 Closing log

...and so far i cannot seem to repro this on linux or winnt, either. :(

looks like something in layout.

Sairuh, is that the right macsbug log you posted on 2001-07-02 16:30? It looks like a printing log... I'm still working on reproducing this one.

marc: yep, that's the Macsbug stack crawl i got when i crashed in this bug. sometimes the talkback info and the Macsbug info are different (strange, but true :). i'd double-check the talkback info, but the server seems to be down at the moment...

just crashed again with this bug, and the Macsbug stack crawl is the same as above...

Hmm - so why are we creating a print context... BTW: I just reproduced the crash too (but my stack was way different). Accepting.

*** Bug 84328 has been marked as a duplicate of this bug. ***

May God have mercy on us all. The 212 bug spam-o-rama is Now!

I would ignore the macsbug log in this case -- the branch builds have the symbols disabled (as happens right before release), so you're only seeing exported symbols, or something like that. (Notice the large offsets from the functions.) But this is really just a duplicate of bug 89626.

So, then like bug 89626, this is fixed? I'll verify and dup it then. Thanks David.

I cannot reproduce this anymore (using 0.9.4 branch or trunk builds, OS9). Marking as a dup of 89626 as suggested by David Baron. *** This bug has been marked as a duplicate of 89626 ***