[GFX1-]: [OPENGL] Failed to init compositor with reason: FEATURE_FAILURE_OPENGL_CREATE_CONTEXT
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: tnikkel, Unassigned)
Details
Attachments
(1 file)
262.99 KB,
text/plain
|
Details |
I recently experienced an unusual failure on my machine. During this time period it would take 30+ seconds to open any new window or dialog. I started a separate browsing session and in the console I had several copies of the error in the bug title and that session was also very slow to open new windows.
Some context: I run beta for my main browsing session. For a long time now I've been getting slowly increasing heap unclassified in my main process. At the time of this problem it was 3.3 GB, I usually restart more frequently for it never gets that bad.
Aftering quitting the browser sessions with 3.3GB heap unclassified everything seemed to be working fine again.
Reporter | ||
Comment 1•4 years ago
|
||
On beta with mostly default settings, so no-webrender.
Reporter | ||
Comment 2•4 years ago
|
||
I can probably reproduce, I just need to keep my browser running for ~two weeks again. So if there are any steps you'd like to take to investigate I can do that.
Comment 3•4 years ago
|
||
Can you attach an about:memory report from the next time it happens?
Comment 4•4 years ago
|
||
I'm not sure what kind of performance impact DMD has these days but you could try running nightly with DMD=1 and see if that can report on the heap unclassified.
Reporter | ||
Comment 5•4 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)
Can you attach an about:memory report from the next time it happens?
Sure. I can attach it in a few days when the heap-unclassified grows to be unreasonably but not crazy, that might help. And then I'll try to do the same when it gets crazy again.
Reporter | ||
Comment 6•4 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #4)
I'm not sure what kind of performance impact DMD has these days but you could try running nightly with DMD=1 and see if that can report on the heap unclassified.
This is in my main profile which I run on beta. I don't want to convert my main profile to nightly for this. Months back I tried to make a DMD build of beta but I ran into a build error that I didn't see an obvious way to fix which made me think that beta dmd builds was not a thing that was supported. I then made a copy of my main profile and let it run with a dmd build for quite a while without interacting with it but that didn't reproduce the heap-unclassified problem.
Note that I am not the only person seeing large heap unclassified on mac: bug 1625590.
Reporter | ||
Comment 7•4 years ago
|
||
The heap-unclassified problem isn't a new thing, I've had it pretty much the entire time I've been using this machine (7 months).
Comment 8•4 years ago
|
||
I'll try running my profile with DMD
Updated•4 years ago
|
Reporter | ||
Comment 9•4 years ago
|
||
heap-unclassified is approaching 3GB again, I expect to be able to reproduce this soon. Anything else I should try when my Firefox/system is in that state?
Reporter | ||
Comment 10•4 years ago
|
||
I'm well past 3GB heap unclassified and haven't had the problem yet. I realized that I won't be able to save a memory report because file dialogs do not open if your Firefox has been updated out from under you (ie another instance updated it while you were running).
Reporter | ||
Comment 11•4 years ago
|
||
clearing needinfo, I've done the best I could to get more info. If it happens again I'll try to get more info and post it here.
Reporter | ||
Comment 12•4 years ago
|
||
It happened again. This time I remembered that you can cut and paste about:memory.
Reporter | ||
Comment 13•4 years ago
|
||
I believe I had webrender during the "early beta" period and it seemed like heap-unclassified climbed quicker, but I didn't run into this error.
Description
•