Closed Bug 1383116 Opened 7 years ago Closed 5 years ago

Running FF with OGL layers ends up locking the entire machine

Categories

(Core :: Graphics, defect, P3)

54 Branch
Unspecified
Linux
defect

Tracking

()

RESOLVED INCOMPLETE
Tracking Status
firefox57 --- fix-optional

People

(Reporter: jya, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

With a Dell XPS 15 (model 9560), only using the intel IGP, whenever I run Firefox with the OpenGL accelerated layers, the system ends up locking up.

It's not consistent, but over the course of a day it will typically happen a 3-4 times.

Seems to be more likely to occur when you have a video playing and you're loading a new page.

When the hang occurs, the keyboard and trackpad becomes unresponsive and it requires a hard reboot.

I never get a lock when accelerated layers are disabled (default).

This is with Ubuntu 17.04 and kernel 4.10.14, though I had the same behaviour running Ubuntu 16.04 and 16.10 (With their respective default kernel)

Whatever FF is doing with it's OpenGL code, it's triggering a bug in the drivers.
To add, I used Chromium for a day, and never got a lockup.
Whiteboard: [gfx-noted]
> Whatever FF is doing with it's OpenGL code
> it's triggering a bug in the drivers.

Considering how servere this issue is - shouldn't it be immediatly reported at the Mesa bugtracker at freedesktop.org?
So.. I gave a quick look to freedesktop's intel firefox-freezing issues

https://bugs.freedesktop.org/show_bug.cgi?id=102512
https://bugs.freedesktop.org/show_bug.cgi?id=102586
https://bugs.freedesktop.org/show_bug.cgi?id=103584
https://bugs.freedesktop.org/show_bug.cgi?id=104222
https://bugs.freedesktop.org/show_bug.cgi?id=104882

Possibly, one of the many ones might have been fixed just some day ago in latest git. 
Any chance for checking it out?

(In reply to Jean-Yves Avenard [:jya] from comment #0)
I assume you're using WebRender by now and haven't seen this problem anymore?

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.