Closed Bug 1506831 Opened 6 years ago Closed 5 years ago

The Firefox browser crashes on Google Maps

Categories

(Core :: Graphics: CanvasWebGL, defect)

Desktop
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox63 --- affected
firefox64 --- affected
firefox65 --- affected

People

(Reporter: rdoghi, Unassigned)

Details

Crash Data

[Affected versions]: 
Nightly 65.0a1

[Affected platforms]:
Platforms: MAC OsX 10.12 Sierra


[Steps to reproduce]:
1. Open the Firefox browser and open a few websites in new tabs (facebook, gmail, Youtube, Amazon, Bing, Twitter, Pinterest, Instagram, reddit, twitch, cnn).
2. Reach https://www.google.com/maps/@40.3870523,-3.6669787,14.07z and play with the Map (Zooming in and out, move it around)
3. Switch tabs and return to google maps.


Expected Result:
The User should be able to play with the map without any issues.

Actual Results:
The Google maps tab crashed twice.

Crash Reports
https://crash-stats.mozilla.com/report/index/bd449e52-bdbf-4f83-9a04-dbaea0181113
https://crash-stats.mozilla.com/report/index/9b53a940-ffd0-41c4-b193-489cd0181113

Please note that I only managed to reproduce this issue twice on the latest Nightly 65.0a1 (2018-11-12), I wasnt able to reproduce it on Beta or Release version.

I also tried reproducing this on Windows and Ubuntu but without any success.
Based on the Crash reports I noticed that this issue did in fact occur on the Release version as well as Beta.
We'll have to wait until Bug 1506781 is address to figure out what the real crash signature is - both of the reports above have the empty signature.
[@ _sigtramp ] is one of the signatures, which maps to Bug 1421182, which describes Google Maps crashes with Intel HD Graphics 3000. So this is likely a dupe of that bug.
Crash Signature: [@ abort | GLEngine@0xb2225]

Seems like that crash sig hasn't happened in months, so closing this bug for now.

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.