WebRender Crash in GeForceTeslaGLDriver@0x2e9cd4 on macOS
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
People
(Reporter: abr, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
This bug is for crash report bp-f2b070a4-ae72-4722-ac44-ff4950190204.
Top 10 frames of crashing thread:
0 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x2e9cd4
1 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x2e47ce
2 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x2df00d
3 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x2ed203
4 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x2edcaf
5 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x202042
6 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x201399
7 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x2ec762
8 GeForceTeslaGLDriver GeForceTeslaGLDriver@0x2dad20
9 GLEngine gleDoDrawDispatchCoreGL3
See also bp-95449ebf-b9b1-4a11-82f8-de6dd0190204
This bug was reproducible (i.e., it crashed and then crashed again on startup), but I had a lot of tabs open and had to dump session state to get the profile working again. I'll update this but with an STR if I come across the offending page again.
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
Reporter | |
Comment 1•5 years ago
|
||
Happened again, but didn't crash on restart, so still no STR: bp-fe4ac7e2-5c74-44f9-8cde-0b8160190204
|
|
||
Comment 2•5 years ago
|
||
Have you been running with WebRender for a while? i.e. do you think this was caused by a webrender regression or by encountering some new content that you hadn't before?
|
|
Reporter | |
Comment 3•5 years ago
|
||
I've been running with 'gfx.webrender.all' for quite a long while now, and the crashes just started this morning. I'm up to four for the day (add bp-f954934d-ca83-4c07-8851-e83e90190204 to the pile).
If there's a pattern here, it might have to do with minimizing a window right after closing a tab: when I'm done with a task, I'll frequently do command-W / command-M in fairly rapid succession, and that's definitely what I did this right before this most recent crash. I think that lines up with the other crashes as well, since I don't recall the annoyance of being in the middle of a task and having Firefox crash out from under me.
Update history shows that I went from 66.0b3 to 66.0b4 on Friday afternoon. Since I don't use this machine much except for work, it would have gone untouched over the weekend. So it seems extremely likely that this is a 66.0b3 -> 66.0b4 regression. Did something get uplifted?
|
|
Reporter | |
Comment 4•5 years ago
|
||
I'm now up to 13 of these over the course of a couple of days (I'm now on 66.0b5), but still have no reliable STR. However, if anyone is trying to track this down and can't repro, reach out to me and I'll do what I can to capture information. While I can't trigger these on command, I'm pretty sure to encounter this crash several times through a normal day of use.
|
||
Comment 5•5 years ago
|
||
Closing because no crashes reported for 12 weeks.
Description
•