User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 Build ID: 20150609081916 Steps to reproduce: 1. Start Firefox. 2. Click on File → Quit, or hit Ctrl-Q. Actual results: Nothing happens. Expected results: Firefox should quit.
Hello Can you reproduce the issue in Safe Mode? If yes and you can reproduce the issue in Safe Mode, can you still reproduce it even with clean new fresh profile without any addons (extensions and plugins)? You can also try a standard troubleshoot and diagnose procedure. Next time please write bug reports in standard ways, especially when you use pre-alpha build which is Nightly.  = https://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode  = https://support.mozilla.org/kb/refresh-firefox-reset-add-ons-and-settings  = https://support.mozilla.org/kb/troubleshoot-and-diagnose-firefox-problems  = https://developer.mozilla.org/en-US/docs/Mozilla/QA/Bug_writing_guidelines
I couldn't reproduce the issue in Safe Mode. The problem could be reproduced all the time without Safe Mode earlier today. But now I can no longer reproduce the problem at all, though I haven't changed anything, except switching to Firefox 38 in the mean time.
The problem occurs again. I've attached the about:support data.
Another about:support with a smaller set of enabled extensions for which I get the problem (but still not always). I tried to disable another extension (I've tried on 3 different ones), but couldn't reproduce the problem with such a smaller set.
Attachment #8620534 - Attachment is obsolete: true
So it's an extension issue, so it's more like a WONTFIX, but still Firefox should force shutdown if user ordered it to. Next question if you use "Quit" what happens? Nothing - browser doesn't shutdown or it shutdown, but it stays in task manager as process?
(In reply to Virtual_ManPL [:Virtual] from comment #5) > So it's an extension issue, Why would that be an extension issue? In particular, I don't see why simple extensions that have an effect on the reproducibility would be the cause of the problem. At least Firefox should provide information on what happens (some log or whatever). > Next question if you use "Quit" what happens? > Nothing - browser doesn't shutdown > or it shutdown, but it stays in task manager as process? The browser doesn't shutdown, and I can still use it as if I didn't use "Quit". Note that sometimes (but not always), the "File" item remains highlighted for a fraction of second. So, it seems that something happens, but with no effect.
Exactly, I agree, even if it's extension issue, Firefox shouldn't behave that way.
Severity: normal → major
Status: UNCONFIRMED → NEW
Component: Untriaged → General
Ever confirmed: true
Product: Firefox → Core
Version: 41 Branch → unspecified
Firefox add-ons have full power on it, they can do anything and we don't have much control over what they do (apart from the AMO review that mostly is a defense against malware). This is one of the reasons extensions are so powerful and useful in Firefox. Could you please try to figure out which extension causes the problem? Then by looking at its code we might be able to tell more.
Component: General → General
Product: Core → Firefox
There are at least Flagfox, gTranslate, HeadingsMap, and NoScript, which can be involved. However since the bug doesn't always occur with a same set of extensions, I can't be sure. That's why debugging information from Firefox would be useful.
@ Marco Bonardo [::mak] - But even power to control closing? For me it seems like a kinda too big power, which can lead bad written extension to take control over browser and user control. @ Vincent Lefevre - You can try to use Error Console or Browser Console/Web Console to see errors and warnings related to extensions.
Extensions have the same rights as Firefox itself. So yes.
(that said, if by looking at the add-on code it's possible to add some defensive code, it's welcome)
(In reply to Virtual_ManPL [:Virtual] from comment #10) > @ Marco Bonardo [::mak] - But even power to control closing? For me it > seems like a kinda too big power, which can lead bad written extension to > take control over browser and user control. There's even an API for it: https://developer.mozilla.org/en-US/docs/Observer_Notifications#Application_shutdown If someone wants to hunt for addons mis/abusing this, searching the source of all addons on AMO for "quit-application-requested" and checking if they muck with it would find that. (there's a Mozilla internal DB for doing these searches; I don't have access to it) That said, I'd expect a bug in handling something else on shutdown is at fault here.
You need to log in before you can comment on or make changes to this bug.