Denne tråd blev arkiveret. Stil et nyt spørgsmål, hvis du har brug for hjælp.
FireFox 65.0.1 crashes (many times) with a "Mozilla Crash Report" and FireFox does not close - "Firefox is already running, but is not responding..." WHY?!
FireFox 65.0.1 crashes with a "Mozilla Crash Report" everytime I use it.
And FireFox does not close - "Firefox is already running, but is not responding...".
Problem appears to have started after attempting to use "Content Blocker" (wanted to block "doubleclick.net". Resetting to defaults does not stop the problem.
How do I stop this?
Should I remove FireFox 65.0.1 and revert to an earlier version that works?
Alle svar (7)
hello, could you provide your latest few submitted crash reports? please enter about:crashes into the location bar, copy the latest few report ids from there starting with bp- & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.
Since 02/19/2019 I have submitted 14 crash reports, and they are still happening!
Mozilla Crash Reports Search Sign in Quick Navigation • Select Product • • Select Version: • • Report: • Documentation | File a bug | Super Search Firefox 65.0.1 Crash Report [@ shutdownhang | mozilla::net::nsStandardURL::SetSpecWithEncoding ] Search Mozilla Support for this signature How to read this crash report ID: c56be918-fe78-401f-b92a-c80bb0190221 Signature: shutdownhang | mozilla::net::nsStandardURL::SetSpecWithEncoding • Details • Metadata • Bugzilla • Modules • Raw Dump • Extensions • Telemetry Environment • Correlations Signature shutdownhang | mozilla::net::nsStandardURL::SetSpecWithEncoding More Reports Search
UUID c56be918-fe78-401f-b92a-c80bb0190221 Date Processed 2019-02-21 22:07:23 UTC Uptime 908 seconds (15 minutes and 8 seconds) Last Crash 1,715 seconds before submission (28 minutes and 35 seconds) Install Age 366,265 seconds since version was first installed (4 days, 5 hours and 44 minutes) Install Time 2019-02-17 16:19:12 Product Firefox Release Channel release Version 65.0.1 Build ID 20190211233335 (2019-02-11) Buildhub data
Mozilla Crash Reports Search Sign in Quick Navigation • Select Product • • Select Version: • • Report: • Documentation | File a bug | Super Search Firefox 58.0.2 Crash Report [@ IPCError-browser | ShutDownKill ] Search Mozilla Support for this signature How to read this crash report ID: 591bd3be-f106-41ea-bcc8-753f60190221 Signature: IPCError-browser | ShutDownKill • Details • Metadata • Bugzilla • Modules • Raw Dump • Extensions • Telemetry Environment • Correlations Signature IPCError-browser | ShutDownKill More Reports Search
UUID 591bd3be-f106-41ea-bcc8-753f60190221 Date Processed 2019-02-21 22:08:58 UTC Uptime 1,064 seconds (17 minutes and 44 seconds) Install Age 1,273,476 seconds since version was first installed (2 weeks, 17 hours and 44 minutes) Install Time 2018-02-22 00:31:50 Product Firefox Release Channel release Version 58.0.2 Build ID 20180206200532 (2018-02-06) Buildhub data
thanks, those reports show that you are running multiple ad-/content blockers at the same time which is a recipe for causing problems. please refresh firefox and then just stick to a single addon in this category - i'd recommend https://addons.mozilla.org/firefox/addon/ublock-origin/
I have been using Adblock Plus for years and have great faith in it so I removed uBlock Origin.
No change (actually I did not expect a change). FireFox still crashes on exit. Based on your comments and the history of uBlock Origin (and uBlock), I will consider it an undesirable Add-on.
I did note that, per Task Manager, FireFox was taking 65 or more seconds to close. My laptop is running FireFox 65.0.0 (I have been afraid to update it) and does not have this problem.
My first thought was to figure out how to replace 65.0.1 with 65.0.0, but it looks like Mozilla has "fixed" FireFox to prevent this.
Then I started comparing settings and found that on my desktop, Menu>Content Blocking>Cookies and Site Data was set to "Delete cookies and site data when FireFox is closed". I am not a fan of cookies and/or tracking. Removing this setting appears to have solved the problem.
Sadly, I have to assume that deleting cookies (and site data) is NOT strongly supported by Mozilla, therefore causing it to crash (maybe do other things in that 65+ seconds.
Thank you for your input. I'm sure FireFox will have more problems soon.
You can let the cookies expire when Firefox is closed to make them session cookies instead of using "Clear history when Firefox closes" to clear the cookies.
- Options/Preferences -> Privacy & Security
Firefox will: "Use custom settings for history" -> Cookies: Keep until: "I close Firefox"
You can create an Allow exception to keep specific cookies.
You can set network.cookie.thirdparty.sessionOnly to true on the about:config page to make third-party cookies behave as session cookies that expire when Firefox is closed.
Ændret af cor-el den
First, your full post did not come through in email.
Second, I can not find "Use custom settings for history" --> Cookies: Keep until: "I close Firefox".
BTW: 86% of cookies were persistent cookies (remain on a person's device after use). 14% were session cookies (removed after a person's browsing session has ended). The average cookie is set to expire after one to two years but some cookies were being set for as long at 10, 100 or even nearly 8000 years.
I can't wait that long.
Keep until would be "Delete cookies and site data when Firefox is closed" in the first screenshot. Using this choice you can create an allow exception for cookie you want to keep.
If you click the text in the second screenshot after "Firefox will" then you will find the "Use custom settings for history" choice that allow to inspect and modify individual choices.