I will say that this particular bug/issue/whatever has been around for quite a while.

Hmm. Much as I’m loath to get too involved with one corporation, even if it is a hometown outfit, I do hear there’s a new browser in town…

that’s exactly what i’m saying, yes.

what you are seeing is a crash, and
_not_ a quit that intends that dialog.

> when all you’re asking it to do is
> shut down–no multiple tabs to be saved,
> no files being loaded…

bugs can exist in a variety of forms,
including ones that act _consistently_,
even in places where a lay observer
might think “nothing is being done”…

those get found — and fixed — quickly.

-bowerbird

On the other hand, there is a Vista curiosity…it always starts up pretty rapidly (I’m guessing 45-60 seconds for startup to complete), and usually shuts down in 30 seconds or less–but once in a while, even though the UI shuts down right away, it takes 2-3 minutes for the notebook’s power light to go off. That’s probably either cache updating or indexing…

One thing to know about crash reports is that, according to the Mozilla knowledge base, they aren’t acted on unless (extracted from the bottom of the Firefox Crashes page):

[you] post on the Firefox Support forum what steps cause Firefox to crash and your … Breakpad report ID. Those who read it may be able to look up your crash on the Talkback website and find an existing bug report or file a new one for you.
Also, if the crash you experience is common, it may be marked as a “topcrasher”, making it more likely to be fixed in the next release.

You can see the list of crash reports you’ve submitted by putting “about:crashes” in the address bar.

And, based on Lazygal’s comment, it appears I’m not the only one…

i’d say that means the program did not terminate
in the proper manner, but rather (in fact) crashed.

probably not in a way that had any consequences,
since you were quitting anyway, but nonetheless…

-bowerbird