Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Firefox crashes (can't open) certain websites after update

  • 5 odpowiedzi
  • 1 osoba ma ten problem
  • 2 wyświetlenia
  • Ostatnia odpowiedź od thesserd

more options

After i updated Firefox on my iMac, i can't visit certain websites anymore. I get this error message that my tab just crashes (see uploaded screenshot). It happens for example with these websites: https://mhasalmere.nl/, http://www.devreugdehoeve.nl/, https://dijanneriezebos.nl/. I can visit other websites like https://brainstorm.nl/, https://google.com/, https://www.wehkamp.nl/, etc.

I've tried several possible solutions from these pages: https://support.mozilla.org/en-US/kb/fix-problems-connecting-websites-after-updating https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can

But none of those worked.

Hope you guys/girls can help out. Thanks in advance!

Thessa

After i updated Firefox on my iMac, i can't visit certain websites anymore. I get this error message that my tab just crashes (see uploaded screenshot). It happens for example with these websites: https://mhasalmere.nl/, http://www.devreugdehoeve.nl/, https://dijanneriezebos.nl/. I can visit other websites like https://brainstorm.nl/, https://google.com/, https://www.wehkamp.nl/, etc. I've tried several possible solutions from these pages: https://support.mozilla.org/en-US/kb/fix-problems-connecting-websites-after-updating https://support.mozilla.org/en-US/kb/firefox-cant-load-websites-other-browsers-can But none of those worked. Hope you guys/girls can help out. Thanks in advance! Thessa

Wybrane rozwiązanie

You can check for sandbox related security issues.

You can set this pref to 2 or 1 on the about:config page to lower the sandbox security setting.

  • security.sandbox.content.level = 1
  • close and restart Firefox to make the change effective.

If '1' still doesn't have effect then try '0' to disable the sandbox.

If this didn't work then undo/reverse the change and reset the pref via the right-click context menu to the default value.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.


You can create a new profile to test if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

Przeczytaj tę odpowiedź w całym kontekście 👍 1

Wszystkie odpowiedzi (5)

more options

Hmm, it looks like my screenshot wasn't added to the post. So here it is.

What also may be important to know, i can open those websites in Chrome and Safari.

Zmodyfikowany przez thesserd w dniu

more options

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.

aboutcrashesFx57

For more help on crash reports, see; https://support.mozilla.org/en-US/kb/firefox-crashes-asking-support

more options

Thanks for your reply Fred. I can't seem to add bp- in front of the reports. Check the screenshots screenshots. The page with all the ???? opens if i click one of the crash reports.

Anyway, not sure if this is usefull now but here are the most recent reports: 1B847F1C-C6DA-4151-8BFA-91B005E481FB 23-05-18 12:13 DA9D9593-3D3B-420F-8A37-A2DC73C6BF08 23-05-18 12:01 E1A5C004-B8EF-4914-9050-ADE61B6290A2 23-05-18 11:58 462E4515-040F-4270-A91E-6F32E4BC01A1 23-05-18 11:58 3BE6761D-6027-4E08-B8D1-32CF3319379B 23-05-18 11:58 50AB52D9-DF41-49E9-98C2-394F63AED5FC 23-05-18 11:58 7947077C-9690-40CA-8225-4C472E644495 23-05-18 11:58 B6CF2D51-1E96-4D2D-8CA9-A6B43E119B49 23-05-18 11:58 8B3AC161-2FD7-43C6-BAE0-0D5628819A03 23-05-18 11:57 1E7AD1B0-19FD-4599-B58E-8C3739D51EBC 23-05-18 11:57

-edit- I now see that only clicking it already did the job, sorry ;) hereby: bp-404258a7-5f1f-4c36-8b8c-8a00e0180523 23-05-18 12:38 bp-73c8d5f5-88c3-44f6-bf6b-952510180523 23-05-18 12:35 bp-e390d9e6-9a59-40a6-b797-e4e720180523 23-05-18 12:35 bp-c08d5b73-ed5c-4e69-8b48-455491180523 23-05-18 10:56 bp-bccd56b2-9cf3-4397-a563-815081180523 23-05-18 10:52 bp-a0d929f7-0ba8-41a3-bbd5-29aa81180523 23-05-18 10:52 bp-875bcee9-18fa-413d-b1d2-57b001180523 23-05-18 10:52

Zmodyfikowany przez thesserd w dniu

more options

Wybrane rozwiązanie

You can check for sandbox related security issues.

You can set this pref to 2 or 1 on the about:config page to lower the sandbox security setting.

  • security.sandbox.content.level = 1
  • close and restart Firefox to make the change effective.

If '1' still doesn't have effect then try '0' to disable the sandbox.

If this didn't work then undo/reverse the change and reset the pref via the right-click context menu to the default value.

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.


You can create a new profile to test if your current profile is causing the problem.

See "Creating a profile":

If the new profile works then you can transfer files from a previously used profile to the new profile, but be cautious not to copy corrupted files to avoid carrying over problems.

more options

@cor-el, the sandbox thing solved it! I set the value to 1 and it worked right away. Thank you very much.