1208210 - Just loaded Firefox 41.0 on a Win 10 64-bit machine and whenever I have a couple of tabs open it quits responding. I have to use the Task Manager to cancel the process.

Status: RESOLVED DUPLICATE of bug 1207766

(Firefox :: Untriaged, defect)

Description

[Ron Ponec]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:41.0) Gecko/20100101 Firefox/41.0
Build ID: 20150917150946

Steps to reproduce:

Opened Drudge Report in main window then just opened two or three linked stories in different tabs. (Happens on numerous sites not just Drudge.)


Actual results:

On the top left corner of the browser I get the message that Firefox is not responding and is completely locked up.


Expected results:

I should be able to pull up multiple tabs linked to different sites without causing a lockup just like it worked a couple of release ago.

Comment 1

[Ron Ponec]

I had this problem on the previous release but to a lesser extent.  The browser would give me a "not responding" error but then resolve itself and continue on.  This happened a couple of times a minute if I was going through a number of tabs (2-7).  This latest release just plain locks up and stays that way.  My system is up to date on drivers.

Comment 2

[besrml]

From previous release of Fx 41(beta or aurora) was getting the browser hanging, after a refresh and disabled  oop for flash in mms.cfg and the plugin setting was resolved.

With the release of Fx 41(release channel) the problem got back, I have restricted to the process plugincontainer, kill it and the browser got responsive again.

The hang of plugincontainer is intermitent and don't get any report(doesn't crash).

In related websites say is related to dom.ipc.plugins.asyncInit setted to true, but in my case is false already. Was the flash plugin whitelisted to async comunication?

Perharps i need another option to complete disable the async options for the addons.

The workaround was revert back to Fx 40.0.3

Comment 3

[Bob Owen (:bobowen)]

Hi Ron,

I suspect this is one of the two hangs (which are very similar) from bug 1207766 or bug 1209235.
They seem to have been masked (at least partially) when Fx41 was in Beta.

Would you mind testing in current Beta (Fx42) with the following pref set (in about:config):

dom.ipc.plugins.asyncInit=false

We think they are now fixed by another change and we are looking into uplifting that fix.

Comment 4

[Ron Ponec]

I tested this out with Beta (Fx42) on my machine at the office and so far it seems to have taken care of the problem.  The browser does seem to get a bit "twitchy" but it is resolving itself in short order.  It's worlds better than it was anyway.

I'll be testing this on my home machine when I get there tonight.

Comment 5

[Ron Ponec]

Just a follow-up...

I have tested the Beta (Fx42) extensively on both my machines and have not suffered even one stoppage.  The browser behavior does get a little choppy with multiple tabs open but it keeps chugging along.

Two thumbs up for the Beta fix!

-Ron

Comment 6

[Bob Owen (:bobowen)]

(In reply to Ron Ponec from comment #5)
> Just a follow-up...
> 
> I have tested the Beta (Fx42) extensively on both my machines and have not
> suffered even one stoppage.  The browser behavior does get a little choppy
> with multiple tabs open but it keeps chugging along.
> 
> Two thumbs up for the Beta fix!
> 
> -Ron

Thanks for testing this!

The fix has gone into 41.0.1, so if you upgrade you should get it for release.