Firefox crashes
Since the new update firefox 60, it hangs after a few moments or pages. We have to perform a forced stop to restart firefox. We have the problem on the 2 imac, and the 2 macbook pro. Software is up to date . We send a crash report every time. We never had any problems with previous versions.
Thanks Steven
Все ответы (8)
Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.
A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
While still in Safe Mode,
In the address bar, type about:crashes<enter>. Note: If any reports do not have BP- in front of the numbers/letters, click it to submit them.
The crash report is several pages of data. We need the report numbers to see the whole report.
Using your mouse, mark the most recent 7 - 10 crash reports, and copy them. Now go to the reply box and paste them in.
For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support
Rapport-ID Verzenddatum bp-c8fa50ef-b3ea-422f-940b-1f7890180530 30/05/18 13:52 bp-fd6b20b4-7891-4cdf-adc0-1a3f40180530 30/05/18 13:45 bp-53889045-4b60-4b2d-85f9-b0a850180530 30/05/18 10:12 bp-7f9c2889-92bb-43c7-b9eb-ea1980180529 29/05/18 21:00
Product Firefox Release Channel release Version 59.0.2 Build ID 20180323154952 OS OS X 10.13 OS Version 10.13.3 17D47.
bp-c8fa50ef-b3ea-422f-940b-1f7890180530 Signature: IPCError-browser | SHMEM_CREATED_MESSAGE Payload error: message could not be deserialized
This is for Sumo's Related Bugs 1362303 RESOLVED FIXED Crash in IPCError-browser | SHMEM_CREATED_MESSAGE Payload error: message could not be deserialized ++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 60.0.1 Build ID 20180516032328 OS OS X 10.13 OS Version 10.13.3 17D47
bp-fd6b20b4-7891-4cdf-adc0-1a3f40180530 bp-53889045-4b60-4b2d-85f9-b0a850180530 bp-7f9c2889-92bb-43c7-b9eb-ea1980180529
Signature: shutdownhang | __psynch_cvwait | _pthread_cond_wait | pthread_cond_signal_thread_np
The crash reports flagged these programs; libobjc.A.dylib = ? Word for Mac or libsystem_notify.dylib = unknown or nothing flagged.
This is for Sumo's Related Bugs 1365600 NEW --- Crash in shutdownhang | __psynch_cvwait | _pthread_cond_wait | pthread_cond_signal_thread_np [Mac] (engimail/password)
Normally, shutdownhang means something about the browser did not close properly.
Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.
A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?
While working in safe mode, apparently , there are no crashes anymore...
It could be the work of one of your add-ons, or it could be Hardware Acceleration. How to disable Hardware Acceleration {web link}
Type about:addons<enter> in the address bar to open your Add-ons Manager. Hot key; <Control> (Mac=<Command>) <Shift> A)
In the Add-ons Manager, on the left, select Extensions. Disable a few add-ons, then Restart Firefox.
Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All Of them.
If the problem continues, disable some more (restarting FF). Continue until the problem is gone. After, you know what group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF) until the problem returns.
Once you think you found the problem, disable that and re-enable all the others, then restart again. Let us know who the suspect is, detective.
I deactivated hardware acceleration first and until now, ff didn't "hang" anymore. i'll try the same on the other macs.
thanks Steven
Keep us posted.