Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Firefox constantly freezing up !!!

  • 4 antwoorden
  • 42 hebben dit probleem
  • 7 weergaven
  • Laatste antwoord van shahnoorhossain

more options

Firefox has been freezing constantly for the past 2 days on my Mac Pro, Mac OS 10.8.5, Firefox 35

Have tried the following :

1. Fresh Install 2. Downgrade to firefox 34 3. Closing & unpinning certain tabs 4. Refresh

However ultimately there will come a point where the app will freeze and cease up - consistently when it asks for the master password.

Turning off the master password function has helped but entering back into preferences will crash the app again.

Its not generating crash reports and I was only able to find this possible reference in Console

18/01/2015 21:47:31.000 kernel[0]: firefox (map: 0xffffff801fc1d308) triggered DYLD shared region unnest for map: 0xffffff801fc1d308, region 0x7fff96200000->0x7fff96400000. While not abnormal for debuggers, this increases system memory footprint until the target exits.

Please advise on what I can do to fix the problem.

Regards,

Shahnoor Hossain

Firefox has been freezing constantly for the past 2 days on my Mac Pro, Mac OS 10.8.5, Firefox 35 Have tried the following : 1. Fresh Install 2. Downgrade to firefox 34 3. Closing & unpinning certain tabs 4. Refresh However ultimately there will come a point where the app will freeze and cease up - consistently when it asks for the master password. Turning off the master password function has helped but entering back into preferences will crash the app again. Its not generating crash reports and I was only able to find this possible reference in Console 18/01/2015 21:47:31.000 kernel[0]: firefox (map: 0xffffff801fc1d308) triggered DYLD shared region unnest for map: 0xffffff801fc1d308, region 0x7fff96200000->0x7fff96400000. While not abnormal for debuggers, this increases system memory footprint until the target exits. Please advise on what I can do to fix the problem. Regards, Shahnoor Hossain

Gekozen oplossing

Tried all possible solutions including the ones mentioned (thank you) but failed regardless - in the end - resorted to an HD restoration from a previous backup and then an update to Firefox 35.

This resolved the issue.

Could have been related to firefox or a system fault - I don't know - but just didn't have the energy to waste time exploring anymore.

Thanks for the support though - much appreciated !

Dit antwoord in context lezen 👍 3

Alle antwoorden (4)

more options

Hi shahnoorhossain, Thank you for your question. I understand that there is an issue with Firefox freezing, and it will ask for the master password.

Does this happen in Safe Mode?

more options

A great many Mac users have been having problems. It looks like the issue could be Microsoft programs for Macs. Disable ALL such programs. Is the problem still there?

more options

It is possible that there is a problem with the key3.db file and the logins.json (signons.sqlite) file that store the encrypted names and passwords in Firefox. You can rename the key3.db file (key3.db.old) and logins.json file (logins.json.old) and a possible signons.sqlite file (signons.sqlite.old) or move them to another folder to make it possible to undo the action. You need to set a new Master Password after renaming or deleting key3.db and all currently saved passwords are lost. If that has worked then you can remove the renamed files that are no longer needed. Otherwise you can rename the files to their previous names (key3.db and logins.json).

You can use this button to go to the currently used Firefox profile folder:

more options

Gekozen oplossing

Tried all possible solutions including the ones mentioned (thank you) but failed regardless - in the end - resorted to an HD restoration from a previous backup and then an update to Firefox 35.

This resolved the issue.

Could have been related to firefox or a system fault - I don't know - but just didn't have the energy to waste time exploring anymore.

Thanks for the support though - much appreciated !