Firefox crashes 30-40 times a day
Hello,
When I am using firefox, it crashes 30-40 times a day. I think my drivers are up to date. It is driving me crazy because I use my computer basically all day. Is there a software that it does not work well with? I am wondering if that is the problem. Thanks!
Gekozen oplossing
Firefox comes in three or more folders on all computers. They are;
Maintenance: (Programs Folder) <Windows Only> Firefox itself: (Programs Folder) And two folders in the profile of each user on the computer for each Firefox profile for that user.
If you remove the Firefox folder, the user profiles would not be affected.
Dit antwoord in context lezen 👍 0Alle antwoorden (20)
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 Submitted 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
Hi, Ok i submitted a bunch, back to the end of January, there are a ton more before that. Sorry now the recent ones don't show up to copy so here are some older ones. Its probably the same problem though, I've had it for a long time. Its been getting worse lately though.
8707e85e-b3b7-469d-ae88-39bf203729ce 1/17/2019, 10:51 AM
2da35ff1-43d0-4237-a233-691fc9d6f224 1/15/2019, 12:44 PM
6443881a-f9dc-40ee-961e-cf948d12ac73 1/14/2019, 3:02 PM
9376f141-56ff-42d5-9f21-f7f3d7c9ba22 12/18/2018, 12:05 PM
19de6a7c-c592-47b4-8b70-033ff7c7dec5 12/18/2018, 12:05 PM
f9ccecea-05ec-4621-ae39-ed96473207de 12/14/2018, 2:42 PM
fb05b961-1b4f-4319-a13b-a49044de6e81 12/14/2018, 1:55 PM
ff47c660-ed12-4130-b38f-8c2c4be12d7c 12/13/2018, 12:30 PM
2311035d-93e0-4c28-af1c-e904081842aa 12/13/2018, 12:23 PM
652201c8-c600-494a-a2f2-49883217debd 12/4/2018, 12:55 PM
b3c9aa49-2cee-4db2-a037-7c19cf62e8a7 12/1/2018, 8:45 AM
If a line on the about:crashes page doesn't start with "bp-" then you can click this line to submit the crash report. The link will be updated and gets a "bp-" prefix if the report is submitted successfully.
- please do not add the "bp-" prefix yourself
If you have submitted crash reports then please post the IDs of one or more recent crash reports that start with "bp-".
- bp-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
You can find the report ID of recent crash reports on the "Help -> Troubleshooting Information" (about:support) page.
- click the "All Crash Reports" button on this page to open the about:crashes page and see all crash reports.
Alternatively you can open about:crashes via the location/address bar.
See also:
Here are 4 that happened after I replied to the first person. 3c90677b-1c71-4ad4-a7e4-240aaed2a939 4/8/2019, 5:30 PM da30ad10-3461-4d91-a2d9-ad469d687402 4/8/2019, 5:29 PM 352dd44d-fdf7-45cb-8ef2-d65b254427f6 4/8/2019, 5:23 PM
Nothing with BP
Some of your crash reports weren’t sent to the Mozilla Servers.
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 Submitted 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
Ok, I submitted all of the ones that were not submitted. This should fix the problem?
Crash reports are sent to the Mozilla servers for the techs to look over. They seldom contact the user.
When you give us the report numbers, we look up the reports and try to help you fix the issue.
FredMcD said
Using your mouse, mark the most recent 7 - 10
Submitted crash reports, and copy them.
Now go to the reply box and paste them in.
Hi, this was from yesterday, is that what you are looking for? The queue is cleared now since I submitted all of them unless you have a link to check elswhere.
3c90677b-1c71-4ad4-a7e4-240aaed2a939 4/8/2019, 5:30 PM da30ad10-3461-4d91-a2d9-ad469d687402 4/8/2019, 5:29 PM 352dd44d-fdf7-45cb-8ef2-d65b254427f6 4/8/2019, 5:23 PM
Ok, just saw your last reply above. Thanks. Hope this was what you were looking for.
This just happened
2d4ef067-d8b1-44de-8776-0550801b5b14 4/9/2019, 9:05 AM
bp-5c80e2c6-9abb-4ac6-ae4d-f04000190409 4/9/2019, 6:55 AM View bp-51c04b50-2fb3-4a23-9793-4a1da0190409 4/9/2019, 6:55 AM View bp-60fc31da-04f8-4bdc-9ab6-f2b290190409 4/9/2019, 6:55 AM View bp-fcbf09c4-e05c-4de5-a4fa-bdf230190409 4/9/2019, 6:55 AM View bp-1a1ea4db-09ff-461a-a584-dea240190409 4/9/2019, 6:55 AM View bp-25d81c1d-9714-4009-b191-c74850190409 4/9/2019, 6:55 AM View bp-00937381-c503-42db-a706-fbca10190409 4/9/2019, 6:55 AM View bp-5b4aa32b-7fa4-4aff-8be8-bba310190409 4/9/2019, 6:55 AM View bp-8cbd710d-b163-4a17-a017-ac3b30190409 4/9/2019, 6:55 AM View bp-e561f647-9453-4622-ae0f-117a50190409 4/9/2019, 6:55 AM View bp-a6ba21f6-92f6-4ff7-bd81-12b2a0190409 4/9/2019, 6:55 AM View bp-71b7d6e2-37a3-44f0-9ef9-8e65c0190409 4/9/2019, 6:55 AM View bp-e8ff7647-f1bd-477f-b225-28b6f0190409 4/9/2019, 6:55 AM View bp-8f478193-a06d-49e5-a0bc-3a0760190409 4/9/2019, 6:55 AM
Sat, 14 Jun 2014 00:29:10 GMT bp-5c80e2c6-9abb-4ac6-ae4d-f04000190409
Tue, 19 Apr 2016 22:46:35 GMT bp-51c04b50-2fb3-4a23-9793-4a1da0190409
Thu, 26 Dec 2013 20:30:15 GMT bp-60fc31da-04f8-4bdc-9ab6-f2b290190409
None of the reports you posted are recent.
Please follow these instructions:
As you posted the above reports, you can now clean out the old reports.
In the address bar, type about:crashes<enter>. At the upper right, press the Remove All Reports button.
Be sure to post any NEW reports.
This is from this morning......
2d4ef067-d8b1-44de-8776-0550801b5b14 4/9/2019, 9:05 AM
If you do not SUBMIT your crash reports, we have no way of checking them out.
I did,I submited all of tjhem there is nothing in the queue.
...what about the one I just sent above? It just happened. Here it is again.
2d4ef067-d8b1-44de-8776-0550801b5b14 4/9/2019, 9:05 AM
These 3 just happened. I made a copy before submitting them.
342d1e12-4dfe-4054-b3bd-2e0c644ace84 4/9/2019, 2:51 PM 0e4110a2-3fea-42cc-a595-58cf596c4198 4/9/2019, 2:49 PM bcd8da3a-da4f-4e67-b998-6a0524c5a878 4/9/2019, 2:26 PM
You need to post the modified GUID with a "bp-" prefix that appear after you have submit the crash report. The crash report GUIDs you have posted are of no value because these reports haven't been submitted.
Submit the reports. Then post the New crash numbers.
Ok, got it, here they are.
bp-e2b35e58-7b6a-4d9e-b21c-8837a0190409 4/9/2019, 2:52 PM
View
bp-77042ab5-4f1a-4a1c-9b19-712920190409 4/9/2019, 2:52 PM
View
bp-0ccd3751-ef0a-4005-971d-c07ba0190409 4/9/2019, 2:52 PM
View
bp-388e1021-3f92-4d81-930c-a09940190409 4/9/2019, 2:52 PM
View
bp-d109180d-40c6-4573-929a-d515e0190409 4/9/2019, 3:21 PM
View