[BLOCKER] Crash on quitting Apprunner on Mac

VERIFIED FIXED in M10

Status

()

P3
blocker
VERIFIED FIXED
19 years ago
10 years ago

People

(Reporter: sdagley, Assigned: waterson)

Tracking

Trunk
PowerPC
Mac System 8.5
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

19 years ago
The Mac is crashing on quit in XULDocumentImpl::~XULDocumentImpl() on the call to
observer->DocumentWillBeDestroyed(this).

This is when just running Apprunner in the default config which loads a single
browser window showing mozilla.org.  On quit we make 16 calls to
~XULDocumentImpl().  The first 15 calls get 0 observers on the call to
mObservers.Count().  On the 16th mObservers.Count() returns 13 when quitting but
only 11 when closing the browser window.  I haven't determined what causes the
diff but will add more comments to the bug if I get a chance to investigate
further.
(Reporter)

Updated

19 years ago
Severity: major → blocker
Summary: Crash on quitting Apprunner on Mac → [BLOCKER] Crash on quitting Apprunner on Mac
Target Milestone: M10
(Reporter)

Comment 1

19 years ago
Forgot to mention that we're crahing because the aformentioned observer in the
observer->DocumentWillBeDestroyed(this) call has already been disposed of wehn we
call it.  Doh!
(Assignee)

Updated

19 years ago
Status: NEW → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
(Assignee)

Comment 2

19 years ago
Damn. That change wasn't even approved to go in for M10 (or M-whatever). It got
crammed in with another checkin because I was sloppy. I'm going back that piece
of code out (actually, '#if 0' it). Then will debug in M11.

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 3

19 years ago
VERIFIED Fixed on 1999102599 apprunner build for MacOS86.

Comment 4

19 years ago
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL

Updated

10 years ago
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: ckritzer → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.