Jesse Ruderman Reporter
	Description • 17 years ago

Steps to reproduce:
1. Start a debug build of Firefox (from the command line).
2. Click on the Firefox window to focus it.
3. Cmd+Q.

Result:

###!!! ASSERTION: nsAppShell::Exit() called redundantly: '!mTerminated', file /Users/jruderman/trunk/mozilla/widget/src/cocoa/nsAppShell.mm, line 490

I don't know why this didn't turn Tinderboxen orange.  Does this not happen there, or do they use a different method to quit?

	Steven Michaud [:smichaud] (Retired)
	Comment 1 • 17 years ago

This is an old problem.  It's just that my patch has started
complaining about it.

Here's the source-code comment above the assertion:

// This method is currently called more than once -- from (according to
// mento) an nsAppExitEvent dispatched by nsAppStartup::Quit() and from an
// XPCOM shutdown notification that nsBaseAppShell has registered to
// receive.  So we need to ensure that multiple calls won't break anything.
// But we should also complain about it (since it isn't quite kosher).

	Josh Aas
	Comment 2 • 17 years ago

Steven - what is your recommendation about making this a blocker bug? Is this just a warning that we can ignore or silence or something we need to actually fix?

	Steven Michaud [:smichaud] (Retired)
	Comment 3 • 17 years ago

It's an old, old bug (I saw it when I first started working on the
appshell back in April).  I don't believe it has any user-visible
consequences (otherwise somebody else would have discovered it, too).
It may be a sign of something else wrong that's more serious.  But for
itself it's really not worth blocking on.

I actually now regret putting in the assertion.  Should I get rid of
it?

	Jesse Ruderman Reporter
	Comment 4 • 17 years ago

Yes, please.  A bug report should be enough of a reminder that the bug exists.

	Josh Aas
	Comment 5 • 17 years ago

Lets get rid of the assertion and leave a comment.

	Jeff Walden [:Waldo] Assignee
	Comment 6 • 17 years ago

This assertion is the only assertion firing on the Mac debug+leak tinderbox, and it is the only bug preventing assertions from being fatal on that box.

	David Baron :dbaron:
	Comment 7 • 17 years ago

You could also change the assertion to a warning.

	Robert O'Callahan (:roc) (email my personal email if necessary)
	Comment 9 • 17 years ago

BTW you can write this more simply using NS_WARN_IF_FALSE

	Jeff Walden [:Waldo] Assignee
	Comment 10 • 17 years ago

Ah, didn't know about that macro, and didn't read the second comment until after I committed.  In any case, tho, I think this is actually a little more readable, because to use that you need a double-negative.

I'll let Jesse decide whether to mark this bug fixed or to morph it to not hit the warning, as it's blocking his console-spam bug (and we didn't get rid of the console spam, only changed it).

	Mike Connor [:mconnor]
	Comment 11 • 17 years ago

Jesse, please reopen or file a new bug if there's more to do here.

	Jesse Ruderman Reporter
	Comment 12 • 17 years ago

Ok, I filed bug 402497 on fixing the warning.