Firefox hangs on logoff

[nooby]

I searched the forum but could not find a solution to this issue.

I use Windows 7 Ultimate x64, Firefox 4.0.1 and NoScript v2.1.1.2rc1.

Whenever I logoff or shutdown the computer with Firefox still open, Windows cannot automatically close Firefox ("Firefox process prevents Windows from being closed"). Then, the Firefox process needs to be closed by force.

There's no problems when manually closing Firefox. Also, with Noscript disabled, Windows is able to normally close Firefox on logoff.

Hopefully you can fix this. Please let me know if you want more information.

[Giorgio Maone]

Does this happen also on a clean profile with just NoScript installed?

[nooby]

Hi Giorgio,

Thanks for your quick response.

I backed up and deleted the Mozilla profile folder. It does occur on a clean profile with only NoScript installed.

It also seems to depend on whether NoScript has blocked scripts.
So with Firefox on "about:home", Windows can automatically close it.
But with Firefox on page "http://www.telegraaf.nl" with blocked scripts on it, it hangs on logoff.

Hugo

[Giorgio Maone]

Have you got any security software which injects scripts in webpages, like AVG?

[nooby]

I use Microsoft Security Essentials, of which I am not aware it injects scripts.

To be sure, I tested the issue with the realtime scan disabled. This was unsuccessful, FF still hangs on logoff.

Thanks for looking into this, please let me know if there's more information you need. I would hope this is not caused by NoScript, but it has quite narrowed down to it.

[therube]

I was not able to confirm this.

W7 x86, FF4.

Switch to different (Windows) User.
Open SeaMonkey.
Load a URL on which scripts are blocked.
Leave FF open.
Start | Log Off.

Results: User is logged off.

(In SeaMonkey, you are [by default] prompted to save the session if you had multiple windows or tabs open.)

[GµårÐïåñ]

Microsoft Security Essentials does nothing like AVG or Avast when it comes to the browser or web traffic, even in real-time scanning. It is very unobtrusive and doesn't inject anything. Just so you can eliminate that.

[Giorgio Maone]

I cannot reproduce either.
Please double check in Tools|Add-ons that NoScript is actually the only extension installed.

[Giorgio Maone]

I couldn't reproduce either.
Could you check whether it happens on a different user account?
Does upgrading to Firefox 5 help?

[guest75]

Hi!

After I updated to FF 5.0 yesterday, I then had to re-install an addon. When the install was done, it required a restart. It had opened FF after the install, and when I hit the button to restart now, I got the message that because FF was open that windows couldn't shut down, so I just hit whatever option said go ahead anyway. I thought this was similar to what the op wrote about and just thought i would add it here in case helps with troubleshooting as I have noscript as well. Version 2.1.1.2rc1

It was the first time I had ever had FF open when shutting down or restart and so I just assumed it was a FF or windows protection.

[therube]

> I then had to re-install an addon. When the install was done, it required a restart.

That sounds strange.
What "addon" was it?

[Giorgio Maone]

I got the message that because FF was open that windows couldn't shut down,

Might that be the "You're about to close tabs" modal message?

[Guest75]

What "addon" was it?

The addon was keyscrambler.

Might that be the "You're about to close tabs" modal message?

It appeared to be a windows system message, not a message from within FF. It was sort of like a black screen sort of message, akin to a blue screen, but different.

[Guest77]

Just wanted to add that I was on my desktop, with the small box addon message to restart, over the firefox browser which was not full screen either. So, I could see my desktop and those two items were there as well. I wasn't in firefox, but just on my desktop when I hit the addons restart now, then got the message saying can't close as ff is open, which I could see it was.

[Guest]

Ah, sorry I keep remembering things to add.

The add on program setup was on my desktop, not within FF. FF was only opened as the addon opened it, and I had not gone in the browser, just immediately hit restart.