Closed Bug 1022987 Opened 7 years ago Closed 5 years ago
Firefox often crashes when accessing new Google Maps
My Firefox on Linux64 often crashes when I access the new Google Maps. Here are corresponding crash reports, one for Firefox 30.0: https://crash-stats.mozilla.com/report/index/f1a57f77-c867-4e12-8d42-626a92140608 and one for Firefox 33.0: https://crash-stats.mozilla.com/report/index/f1fd3f3a-0aef-409b-9859-270942140609
Component: General → Graphics
Product: Firefox → Core
This appears to be a null-deref in the linux radeon driver. Maybe we're doing something wrong or maybe the driver is buggy. Hopefully, someone watching the graphics component will have a better idea what's happening with this crash.
I get these crashes on the new Google Maps (which is now the default) very frequently and I don't think that my graphic device is a rare one so I assume that this is a serious problem that somebody should look into. I'm updating importance to P2/Major to reflect that. And here is a new crash report, though probably similar or even identical to the previous ones: https://crash-stats.mozilla.com/report/index/228c877e-9bdf-4a59-b043-e51592140616
Severity: normal → major
Priority: -- → P2
Here is my glxinfo output, maybe it helps to track down the issue: $ glxinfo | grep OpenGL OpenGL vendor string: X.Org OpenGL renderer string: Gallium 0.4 on AMD TURKS OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.1.3 OpenGL core profile shading language version string: 3.30 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 3.0 Mesa 10.1.3 OpenGL shading language version string: 1.30 OpenGL context flags: (none) OpenGL extensions:
Severity: major → critical
Crash Signature: [@ @0x0 | r600_dri.so@0x168a35 ]
The new Google Maps uses WebGL, which I think the old one didn't, and we are in GL code there. There could be some issues with Gallium or Mesa there as well, I guess. The AppNotes from your crash reports mostly restate what your glxinfo tells us as well: OpenGL: X.Org -- Gallium 0.4 on AMD TURKS -- 3.0 Mesa 10.1.3 -- texture_from_pixmap WebGL? libGL.so.1? libGL.so.1+ GL Context? GL Context+ WebGL+
It seems to me that these crashes occur usually (or even always?) when I access Google Maps a second time during one session. The first time it usually works, but when I go to Google Maps again later (after having closed the previous tab, but still during the same session) -> crash.
Could you try if a current (of this week) Firefox 31 beta exposes the same issues? The graphics team did put some great fixes into beta that help with other crash signatures, I'd be interested if it mitigates yours as well.
(In reply to Robert Kaiser (:firstname.lastname@example.org) from comment #6) > Could you try if a current (of this week) Firefox 31 beta exposes the same > issues? The graphics team did put some great fixes into beta that help with > other crash signatures, I'd be interested if it mitigates yours as well. I am using the latest 31 beta. i.e. the beta8 from http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/31.0b8-candidates/build1/linux-x86_64/en-US/
OK, then the patches that helped the other GL-related crashes don't help here, unfortunately. It still sounds to me like it's a problem in the driver (stack), I wonder if you should report it there as well.
Could this be related to garbage collection or something similar? As I said, the 1st time during a session when I access Google Maps it always works. When I access Google Maps a 2nd time later, Firefox crashes. So something must occur between 1st and 2nd accessing of Google Maps which triggers the crash. Garbage collection is one idea which comes to my mind, maybe there are other possibilities?! But it's definitely a lead which I hope gives some developer a clue where and how to investigate this crash further.
(In reply to Markus Popp from comment #9) > Could this be related to garbage collection or something similar? Given the crash data, it sounds more related to your graphics driver stack. It may make sense to report a bug to their driver devs, see http://dri.freedesktop.org/wiki/Radeon/#howtoreportbugs
Bug Report filed at https://bugs.freedesktop.org/show_bug.cgi?id=82109
From my point of view, this bug report can be closed (also freedesktop.org folks closed the report on their side). IIRC, the crashes no longer happened after a Xubuntu upgrade (must have been either from 14.04 to 14.10 or 14.10 to 15.04), likely due to a fixed graphics driver being shipped along with the upgrade.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.