Closed Bug 2884 Opened 26 years ago Closed 26 years ago

[PP] viewer crash: nsWebCrawler::Release called recursively

Categories

(Core Graveyard :: Viewer App, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: akkzilla, Assigned: buster)

Details

Exiting the viewer app through the file menu on Linux causes a crash, with the following stack trace. It looks like nsWebCrawler::Release may be being called recursively? The nsWebCrawler dtor releases mViewer, which turns around and releases nsWebCrawler again, causing a crash. I haven't If this is just a viewer app bug, then it doesn't matter, but I'm filing in case nsWebCrawler is meant to be non-throwaway code (since it still seems to be being worked on). It doesn't crash on Windows, but I'm not sure why (haven't traced the code to watch what happens).
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I fixed the circular issue by removing the reference to the viewer in the web-crawler...
Status: RESOLVED → REOPENED
not fixed...still happens in 2/10 builds...re-opening....Akkana, can you recheck if its the same issue thats causing the crash????
I don't see a crash exiting viewer via the file menu using today's debug build (or yesterday's, either). Sorry, can't confirm or deny ... Kipp's fix fixed it for me. Can you get any sort of a stack trace on the optimized build?
Status: REOPENED → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 26 years ago26 years ago
why is this re-opened? I fixed *this* crash. Don't confuse other crash on exit's with this bug.
QA Contact: 4079
Status: RESOLVED → VERIFIED
verified in 3/2 build.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.