User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:43.0) Gecko/20100101 Firefox/43.0 Build ID: 20160105164030 Steps to reproduce: I work on a webGL project, and after a recent crash it seems that FF now refuses to enable the GPU#2 with wich the crash occured. I have uninstalled and re-installed FF but it has not solved this problem : WebGL doesn't work anymore in FF (while it works in other browsers). Actual results: The about:support page mentions "GLContext is disabled due to a previous crash", and it seems that the GPU#2 (NVIDIA) is always disabled by FF in despite it is enabled by the NVIDIA control pannel. The about:config page : webgl.disabled = false webgl.force-enabled = true > has no effect

Precision : WebGL works in FF Developper Edition

At least since updating to 43.0.4 (maybe all 43 releases) I've had a few crashes with this message shown "GLContext is disabled due to a previous crash". Here's one of my crash reports, libsystem_kernel.dylib@0x17002 https://crash-stats.mozilla.com/report/index/4054d2f7-e459-46eb-8c7e-6733e2160118

(In reply to Stuart Philp :sphilp from comment #2) > At least since updating to 43.0.4 (maybe all 43 releases) I've had a few > crashes with this message shown "GLContext is disabled due to a previous > crash". > > Here's one of my crash reports, libsystem_kernel.dylib@0x17002 > https://crash-stats.mozilla.com/report/index/4054d2f7-e459-46eb-8c7e-6733e2160118 Looks like this crash is happening, at least in part, in the NVIDIA graphics driver. Stuart, did you experience any symptoms before this crash occurred? Have you been able to replicate the crash? Do you recall if you experienced this crash in Firefox 42 or earlier?

libsystem_kernel.dylib@0x17002 seems to be 100% correlated to Mac OS 10.11 users so it's probably not the exact same issue as what jeum reported but the result is the same. Might be worth reporting the crash signature separately since it has 1561 on 43.0.4 which qualifies it as the #6 topcrash on Mac. Milan, can you please advise?

It's an immediate crash to desktop, I believe each time I was closing multiple tabs (cmd-w quickly) but it isn't reliably reproducible. I've seen it maybe 5 times since 43 came out. Don't recall it happening on 42 or earlier.

Thanks Stuart, could you please attach a copy of your about:support page to this bug report?

In my case I believe (not sure) that this crash was caused by an excess of WebGL contexts (kind of thing related to this : http://stackoverflow.com/questions/14970206/deleting-webgl-contexts) I noticed that FF Developper Edition seems more stable for WebGl experimentations. It seems that it manages some things that are not managed by FF (?) when it says : "Error: WebGL: Exceeded 16 live WebGL contexts for this principal, losing the least recently used one".

Jeff, comment 7?

Well I do not have the skills to understand why this problem is related to that bug 1218070.. I want to point out that, for me, this bug has nothing to see with Flash .. (and my OS is Win7) .. However, if you think that it is related, is it possible to have an explanation on how to fix it ?

(In reply to jeum from comment #7) > In my case I believe (not sure) that this crash was caused by an excess of > WebGL contexts (kind of thing related to this : > http://stackoverflow.com/questions/14970206/deleting-webgl-contexts) This could be bug 1224199.

I don't know, I don't understand how to fix it in this case. I made the mistake of doing WebGL experiments on my current browser and WebGL is now permanently disabled on FF ... Uninstall/Install doesn't fix this. I am now forced to get rid off FF and to adopt Chrome, with regret, but I don't know what to do.

A new profile should reset things. So will a new version of Firefox.

Yes ! I have created a new profile and this solved this issue. Copied the whole previous profile folder and it still works fine. Thank you !