Since upgrading to FF 57 Google Maps causes a tab crash. I have tried all of the usual things - clear cache, disable hw acceleration, etc. Pls help.
Mac OSX
Signature abort | glDrawArraysInstanced_STD_GL3Exec More Reports Search UUID 53e89546-9f51-490d-bb33-3ce4e0171121 Date Processed 2017-11-21 20:06:44 Uptime 1,262 seconds (21 minutes and 2 seconds) Install Age 516,930 seconds since version was first installed (5 days, 23 hours and 35 minutes) Install Time 2017-11-15 20:30:54 Product Firefox Release Channel release Version 57.0 Build ID 20171112125346 OS OS X 10.12 OS Version 10.12.6 16G1036 Build Architecture amd64 Build Architecture Info family 6 model 42 stepping 7 | 4 Adapter Vendor ID
0x8086
Adapter Device ID
0x0126
Process Type content (web) Crash Reason EXC_SOFTWARE / SIGABRT Crash Address 0x10a3dc34a User Comments EMCheckCompatibility
True
App Notes
FP(D00-L1100-W00000000-T010) AdapterVendorID: 0x8086, AdapterDeviceID: 0x0126WR? WR- WebGL? GL Context? GL Context+ WebGL+
Processor Notes processor_prod-processor-i-06e515086fb202f35_1385; MozillaProcessorAlgorithm2015; non-integer value of "SecondsSinceLastCrash"
被采纳的解决方案
ok, if turning off hardware acceleration wasn't successfull then please switch it back to the default. in the meantime we've found the following workaround in the associated bug report: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named webgl.1.allow-core-profiles. double-click it and change its value to false and then restart firefox once.
定位到答案原位置 👍 3所有回复 (9)
We're sorry to hear that Firefox is crashing. In order to assist you better, please follow the steps below to provide us crash IDs to help us learn more about your crash.
The crash report is several pages of data. We need the report numbers to see the whole report.
- Enter about:crashes in the Firefox address bar and press Enter. A Submitted Crash Reports list will appear, similar to the one shown below.
- Copy the 5 most recent Report IDs that start with bp- and then go back to your forum question and paste those IDs into the "Post a Reply" box.
Note: If a recent Report ID does not start with bp- click on it to submit the report.
(Please don't take a screenshot of your crashes, just copy and paste the IDs. The below image is just an example of what your Firefox screen should look like.)
Thank you for your help!
More information and further troubleshooting steps can be found in the Troubleshoot Firefox crashes (closing or quitting unexpectedly) article.
hi sjstrey, thanks for reporting this. our developers are aware of this problem and investigating a fix for this in https://bugzilla.mozilla.org/show_bug.cgi?id=1413269 in case you want to follow along.
i guess disabling hardware acceleration may be a workaround for this in the meantime: Firefox's performance settings
Here are my 5 most recent crash reports:
bp-7e9cabe7-d4d2-4d6f-8ea1-9a8890171121 2017-11-21 3:15 PM bp-3ae86ae8-e1ac-4d8b-95e8-aa47e0171121 2017-11-21 3:14 PM bp-8b617116-3577-4930-93f4-33ae90171121 2017-11-21 3:14 PM bp-53e89546-9f51-490d-bb33-3ce4e0171121 2017-11-21 3:06 PM bp-2c783cae-a8b3-4347-9a18-edfa71171121 2017-11-21 2:51 PM bp-b7ebfc24-3485-4873-9b6b-51cce0171121 2017-11-21 2:37 PM
Thanks philipp. Disabling hardware acceleration had no effect, but I appreciate your response and will watch that thread for a resolution.
Cheers
Steve
选择的解决方案
ok, if turning off hardware acceleration wasn't successfull then please switch it back to the default. in the meantime we've found the following workaround in the associated bug report: enter about:config into the firefox address bar (confirm the info message in case it shows up) & search for the preference named webgl.1.allow-core-profiles. double-click it and change its value to false and then restart firefox once.
philipp Thank you for your help. That worked!!
Cheers
Steve
Started to get the same problem since today (Firefox 59.0.1). Config webgl.1.allow-core-profiles is already false. about:crashes is not showing any recent report
Upgraded to 59.0.2 and problem is gone!
great, thanks for reporting back!