![Firefox logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-36-13-8dda6f.png)
how to stop crash reporter from opening even when Firefox doesn't crash? crash reporter opens nearly any time I use Firefox
almost every time I use Firefox, as soon as I quit Firefox, the crash reporter message comes up. how can I make this stop happening? Firefox isn't crashing but the crash reporter is working overtime as if it is!
thanks for your help,
Debbie
การตอบกลับทั้งหมด (20)
This is everytime you shutdown Firefox? This maybe a shutdown hang.
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. Press the Reply button. 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
bp-879495ea-25ab-41dc-a137-9dffc0170602 6/1/17 5:48 PM bp-07b49f20-ebd4-44cc-a182-c6c7c0170602 6/1/17 5:48 PM bp-4c806cbf-cb63-4fd4-b99f-1fc570170602 6/1/17 5:47 PM bp-096481ab-827e-4f2c-8f96-22a3a0170519 5/19/17 4:25 PM bp-334f424d-7213-4d93-b66b-4044f1170519 5/19/17 2:12 PM bp-d8b55c9b-d79b-40d0-9728-703791170518 5/18/17 1:40 PM bp-d6545dbf-4a67-4f39-992c-31eb11170514 5/14/17 7:35 AM bp-5db3e993-1e31-4d14-b636-f4fd51170510 5/10/17 7:25 AM
Product Firefox Release Channel release Version 32.0.1 Build ID 20140911151253 OS OS X 10.9 OS Version 10.9.4 13E28
Why are you using a Very Old version of Firefox? https://support.mozilla.org/en-US/kb/update-firefox-latest-version?cache=no Update Firefox to the latest version 51.0.3
bp-879495ea-25ab-41dc-a137-9dffc0170602 Signature: mozilla::dom::XULDocument::AddPrototypeSheets
This is for Sumo's Related Bugs 878440 NEW --- startup crash in mozilla::dom::XULDocument::AddPrototypeSheets +++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 6.0.1 Build ID 20110830092941 OS OS X 10.5 OS Version 10.5.8 9L30
bp-07b49f20-ebd4-44cc-a182-c6c7c0170602 Signature: F1949931376
This is for Sumo's Related Bugs 678268 VERIFIED FIXED [adbe 2982873] Plugin and Content Flash Crash [@ F1949931376__________________ ] [@ F_363836192______________________________ ] [@ NP_Initialize ] [@ npswf32.dll@0x39c2b3 ] [@ FlashPlayer-10.4-10.5@0x61bfd2 ] +++++++++++++++++++++++++++++++++++++++++++++++++ Product Firefox Release Channel release Version 41.0.2 Build ID 20151014143721 OS OS X 10.9 OS Version 10.9.5 13F1134
bp-4c806cbf-cb63-4fd4-b99f-1fc570170602 Signature: hang | FlashPlayer-10.6@0x68628e
Process Type plugin (web) Shockwave Flash Version: 19.0.0.226
Each crash report is showing a different version of Firefox. What's the story?
I called for more help.
hi Fred,
I don't know why there are different versions of Firefox. I'm using Firefox 53.03. I keep it updated bcz Firefox notifies me when there's an update.
thx for your help,
Debbie
How are you notified? Firefox only updates once in a while.
You should be keeping Firefox up to date, and Firefox normally does that by default unless you changed the settings.
Some of those crash reports may be rather old I notice one old one said last crash 2 years ago. It is possible many recent crashes are duplicate signatures and not getting submitted or processed.
If Firefox is working well and you are not losing information the crash reports are not too important, but if Firefox is hanging or crashing at closedown there is a danger you could lose information, it could be inconvenient for you, and it probably will cause knock on issues and slow startups of Firefox.
If you look in about:crashes do you see any very recent crash reports that are not yet submitted. Those will not start with bp- if you click on them then with a bit of luck they will submit and you will bet the bp- prefix. See if you can submit a few of the most recent crash reports and then let us have the Crash ID for another 3 or 4 of them.
Fred, John, thank you for working on this. I truly appreciate your help. it is driving me mad to have the crash reporter open so very open. it stays in the dock until/unless I close it too!
here is one that just happened that does not have a BP in front of it. ID: f190c7ce-fc8b-4882-a8ce-4ed4c0170602
bp-f190c7ce-fc8b-4882-a8ce-4ed4c0170602
as soon as I clicked on it a page opened that says Firefox 53.0.3 Crash Report (@ Foundation@0xce84) when I click on About Firefox it shows "Firefox is up to date" and is version 53.0.3
Debbie
เปลี่ยนแปลงโดย dlgorham เมื่อ
That seems to be a very uncommon crash signature, near enough unique, whereas some signatures have thousands of related crashes.
It is now submitted and may be found with the bp- prefix.
No point in adding that prefix yourself, unless you see it in your listing because no one else will find the processed report.
Sorry Debbie but I normally use Linux not Mac and although they have similarities there are quite a few differences, so I am not the best person to try to help but the majority here use Windows so I do look at Mac questions as I realise many of them may otherwise go unanswered.
Have you got a couple more recent crash IDs
- Ones that do have the bp- prefix
- And ones where you were in firefox's safe mode
- Please see: Diagnose Firefox issues using Troubleshoot Mode
hi John,
I didn't add the bp prefix myself. when I went to about:crashes and clicked on the latest crash report the prefix appeared.
when I have a few more crash reports I will send them.
I am unaware of any case where I've used Firefox's safe mode.
thx,
Debbie
Debbie, it may be worth trying Firefox's safe mode. That is a very easy to use troubleshooting configuration - all you need to do is hold down the Shift key when you start Firefox, but the crash reports you then get are much more likely to be useful for us those looking at the problem.
John, thx for your suggestion that I try Firefox's safe mode. I will do that the next time I have a crash report. then, when I have a few more, I'll copy and paste and send them to you.
curious why your email says 6:51 AM and online it says 1:51 PM. I'm in Portland, OR. where are you? (obviously I'm not savvy about global time zones...)
Times get very complicated. Your computer will try to display a correct time But it then needs to decide on whether to use the internal time or what for instance an internal clock shows, or maybe check the internet.
After that it has to decide how to display it, and whether to convert it? It may also need to take in to account daylight saying schemes where the time shifts an hour in summer / winter. I think everything looks ok for me.
Right now I see your reply with a plausible reasonable time in comparison to my local time and the order of other replies on the forum. It does not however displays correctly. in my prefered uk dd/mm/yy format it is showing in american mm/dd/yy format but that will be because I am using an en-us version of Firefox Nightly. Ideally everything works correctly & exactly.
hi John,
thx for your reply about time. interesting.
I've been having the same crash reporter problem and will paste in recent report IDs. I've also submitted a number of these most recent crash reports. I don't know what becomes of them, never having had a response from Firefox.
here they are:
bp-055e7355-72cd-4847-a70b-3106c1170607 6/7/17 3:02 PM bp-05fbb5ee-c8fe-4207-9a7f-41bfa1170607 6/7/17 1:50 PM bp-afa90e08-4a25-4d96-8275-b6c4e1170606 6/6/17 8:47 AM bp-99ceea66-d7bc-4f44-85d3-ceb3d1170605 6/5/17 1:20 PM bp-fdd6aa69-babc-438a-9184-fc4cf1170605 6/4/17 7:59 PM bp-96f34c5f-ca4b-4e41-8e9f-9a0211170603 6/3/17 12:07 PM bp-dd099c69-e04f-49e6-8d69-3717b0170602 6/2/17 2:19 PM bp-f190c7ce-fc8b-4882-a8ce-4ed4c0170602 6/2/17 10:04 AM bp-fd0268ab-318c-454c-bf83-3d11b0170602 6/1/17 8:10 PM bp-879495ea-25ab-41dc-a137-9dffc0170602 6/1/17 5:48 PM bp-07b49f20-ebd4-44cc-a182-c6c7c0170602 6/1/17 5:48 PM bp-4c806cbf-cb63-4fd4-b99f-1fc570170602 6/1/17 5:47 PM
thank you for your help. it will be fabulous if you or someone can make the crash reporter stop sending the crash reports since Firefox doesn't crash for me.
best,
Debbie
The crash reports go to the Mozilla servers for the Moz techs to check out. They normally don't make contact with anyone.
bp-055e7355-72cd-4847-a70b-3106c1170607 bp-05fbb5ee-c8fe-4207-9a7f-41bfa1170607
Signature: -[NSWindow setDelegate:]
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS +++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-afa90e08-4a25-4d96-8275-b6c4e1170606 Signature: -[NSView _clearRememberedEditingFirstResponder]
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS +++++++++++++++++++++++++++++++++++++++++++++++++++++ bp-99ceea66-d7bc-4f44-85d3-ceb3d1170605 Signature: -[NSWindow setDelegate:]
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS
Let’s do a full clean re-install; Download Firefox For All languages And Systems {web link}
Save the file. Then Close Firefox.
Using your file browser, open the Programs Folder on your computer.
Windows: C:\Program Files C:\Program Files (x86)
Mac: Open the "Applications" folder. https://support.mozilla.org/en-US/kb/how-download-and-install-firefox-mac
Linux: Check your user manual. If you installed Firefox with the distro-based package manager, you should use the same way to uninstall it. See Install Firefox on Linux; https://support.mozilla.org/en-US/kb/install-firefox-linux
If you downloaded and installed the binary package from the Firefox download page, simply remove the folder Firefox in your home directory. http://www.mozilla.org/firefox#desktop ++++++++++++++++++++++++++++ Do Not remove the profiles folder.
Look for, and rename any Mozilla or Firefox program folders by adding .old to them. Do not rename the Mozilla Thunderbird folder if there is one.
After rebooting the computer, run a registry scanner if you have one. Then run the installer. If all goes well, remove the OLD folders when you are done. +++++++++++++++++++++++++++ If there is a problem, start your Computer in safe mode and try again.
http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode This shows how to Start all Computers in Safe Mode; Free Online Encyclopedia
Updated to version 56.0 and now when I click either the exit option or the X button Firefox closes but still shows as a background process in task manager. Within a couple of minutes or so a crash report pops up on the screen and choosing the close option will send a report and close Firefox. No idea how to correct the issue.
Sounds like not all of Firefox closed 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).
Poke around a few sites. Then close. Is the problem still there?
Tried your suggestion Fred and the problem is still there upon closing.
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode
Safe Mode is a troubleshooting mode that temporarily turns off hardware acceleration, resets some settings, and disables add-ons (extensions and themes). If the problem goes away, that tells us one thing. If it does not, that tells us something else.
Start your Computer in safe mode with network support. Then start Firefox. Try Safe websites. Is the problem still there?
http://encyclopedia2.thefreedictionary.com/Linux+Safe+Mode Starting Any Computer In Safe Mode; Free Online Encyclopedia