Closed Bug 14677 Opened 21 years ago Closed 20 years ago

crash on exiting web crawler


(Core Graveyard :: Viewer App, defect, P3, critical)

Windows NT


(Not tracked)



(Reporter: karnaze, Assigned: rpotts)


(Keywords: crash)

Rick, after running the table regresssion tests and exiting the viewer the
following crash occurs (it is probably the wrong thread, but the others didn't
look very revealing either). This problem came up a day or two before the one
you just fixed (where the webcrawler could not load the 2nd page). I'm not sure
who should get it. Recall to run the test on Windows go to
mozilla\layout\html\tests\table\core and run "rtest baseline".

PR_EnterMonitor(PRMonitor * 0xdddddddd) line 76 + 3 bytes
PL_ProcessPendingEvents(PLEventQueue * 0x00e228c0) line 483 + 12 bytes
_md_EventReceiverProc(HWND__ * 0x00020610, unsigned int 49403, unsigned int 0,
long 14821568) line 970 + 9 bytes
USER32! DispatchMessageWorker@8 + 135 bytes
USER32! DispatchMessageA@4 + 11 bytes
nsNativeViewerApp::Run() line 74
main(int 5, char * * 0x00b113c0) line 136 + 11 bytes
mainCRTStartup() line 338 + 17 bytes
Severity: normal → major
Summary: crash on exiting web crawler → [CRASH] on exiting web crawler
Rick, to run the regression tests and get the crash, do the following on WinNT
(need s drive mapped above mozilla). This bug is making it more difficult to run
the table regression tests which is a bad thing considering that Tinderbox will
be running them.

cd s:\mozilla\layout\html\tests\table\core
rtest baseline
Severity: major → critical
Target Milestone: M15
Viewer-only refcounting problem. Low priority.
Component: other → Viewer App
QA Contact: leger → rickg
Upadting component to Viewer App
Adding "crash" keyword to all known open crasher bugs.
Keywords: crash
Summary: [CRASH] on exiting web crawler → crash on exiting web crawler
I haven;t seen in crashing anymore 2 weeks ago. Is it still a bug?
Moving what's not done for M15 to M16.
Target Milestone: M15 → M16
M16 has been out for a while now, these bugs target milestones need to be 
Worksforme with the 10/4 branch build.
Closed: 20 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.