X
Tippen Sie hierhin, um die Version dieser Website für Mobilgeräte aufzurufen.

Hilfeforum

Firefox crashes

Veröffentlicht

So, about a year ago I upgraded from my rock-solid, uncrashable 5.whatever to whatever the current version was at the time, due to websites not allowing me to pay bills. Then the crashing started. The first couple times, I blew it off, but it was happening almost daily, which was a real problem, so I started allowing firefox to submit crash reports, including my email address, thinking that I'd get a little note telling me I'd screwed something up or the version was buggy or some such, but to date I've yet to receive so much as even a boilerplate gladhand telling me that my problems are due to this or that, or that they got the report. Has anyone ever gotten any assistance from mozilla support this way, or is this the only way to (hopefully) get acknowledgement of issues? Enclosed is a screenshot of the about:crashes page with a list of most of the submitted reports.

I really have enjoyed firefox as a browser, but crashes are a hassle which I don't need, and I really don't want to invest time in learning a new browser. Suggestions?

edit: Evidently, a png image of a list of a couple hundred crash reports doesn't want to be accepted. Said image can be viewed here: http://s1160.photobucket.com/user/unfulfilled17/media/Firefox%20Crash%20Reports.png.html

Thanks

So, about a year ago I upgraded from my rock-solid, uncrashable 5.whatever to whatever the current version was at the time, due to websites not allowing me to pay bills. Then the crashing started. The first couple times, I blew it off, but it was happening almost daily, which was a real problem, so I started allowing firefox to submit crash reports, including my email address, thinking that I'd get a little note telling me I'd screwed something up or the version was buggy or some such, but to date I've yet to receive so much as even a boilerplate gladhand telling me that my problems are due to this or that, or that they got the report. Has anyone ever gotten any assistance from mozilla support this way, or is this the only way to (hopefully) get acknowledgement of issues? Enclosed is a screenshot of the about:crashes page with a list of most of the submitted reports. I really have enjoyed firefox as a browser, but crashes are a hassle which I don't need, and I really don't want to invest time in learning a new browser. Suggestions? edit: Evidently, a png image of a list of a couple hundred crash reports doesn't want to be accepted. Said image can be viewed here: http://s1160.photobucket.com/user/unfulfilled17/media/Firefox%20Crash%20Reports.png.html Thanks

Ausgewählte Lösung

The crash report workflow will ask for email addresses, but only very rarely will developers need to contact anyone for further information.

Only the current Release version (& ESR) is supported. Developers will only try to fix issues in the Release version, so there is little or no point in submitting Crash reports from unsupported versions. If you need help and information on crashes you need to submit the crash report AND then report the Crash ID on this forum

AFAIK the crash report submission does send you an email but it is not personalised enough to even link to the correct actual crash report. {inactive} Bug 765296 - [postcrash] Email individual users after a crash

Firefox 29 was a big and controversial change. Related help articles are

Have you considered the possibility of trying to get Firefox to work and customising it to look and behave more like the older version that you like.

Diese Antwort im Kontext lesen 1

Mehr Details zum System

Installierte Plugins

  • Shockwave Flash 16.0 r0
  • Google Update
  • Adobe PDF Plug-In For Firefox and Netscape 11.0.8
  • Octoshape embedded video plugin
  • Next Generation Java Plug-in 10.55.2 for Mozilla browsers
  • 5.1.30214.0
  • GEPlugin
  • The QuickTime Plugin allows you to view a wide variety of multimedia content in Web pages. For more information, visit the QuickTime Web site.
  • Windows Presentation Foundation (WPF) plug-in for Mozilla browsers
  • MetaStream 3 Plugin r4

Anwendung

  • User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:28.0) Gecko/20100101 Firefox/28.0

Weitere Informationen

FredMcD
  • Top 10 Contributor
4247 Lösungen 59408 Antworten
Veröffentlicht

In the address bar, type about:crashes<enter>. Note: If any reports do not have BP in front of the numbers, click it and select Submit.

Using your mouse, mark the most resent 7 - 10 crash reports, and copy them. Now go to the reply box below and paste them in.

In the address bar, type '''about:crashes'''<enter>.''' Note:''' If any reports do not have '''BP''' in front of the numbers, click it and select '''Submit'''. Using your mouse, '''mark''' the most '''resent 7 - 10''' crash reports, and '''copy''' them. Now go to the reply box below and '''paste''' them in.

Fragesteller

Thanks, Fred, for your punctual reply. Hopefully this is what you want.

bp-a5c7f5ad-f211-4cf8-844e-771942150126 26.Jan.15 15:41 bp-b54bb5f3-23f9-4dc2-b8e1-55d532150126 26.Jan.15 15:26 bp-e6c68fd6-53c2-46fb-978c-d3e2c2150127 19.Jan.15 07:55 bp-331f3811-9c0b-4464-a965-a87bf2150127 17.Jan.15 22:48 bp-4d6d4e49-1c72-4982-a844-72a0f2150127 16.Jan.15 16:16 bp-16b8bbb6-50ac-488f-9b76-e556d2150127 15.Jan.15 09:29 bp-73228909-fa5b-4c28-93bc-fd77a2150127 14.Jan.15 00:17 bp-3e321193-67bb-46a4-b3f2-0e2982150127 12.Jan.15 19:42 bp-f6fa6320-c682-4feb-aa6b-5fb272150127 11.Jan.15 08:13

Thanks, Fred, for your punctual reply. Hopefully this is what you want. bp-a5c7f5ad-f211-4cf8-844e-771942150126 26.Jan.15 15:41 bp-b54bb5f3-23f9-4dc2-b8e1-55d532150126 26.Jan.15 15:26 bp-e6c68fd6-53c2-46fb-978c-d3e2c2150127 19.Jan.15 07:55 bp-331f3811-9c0b-4464-a965-a87bf2150127 17.Jan.15 22:48 bp-4d6d4e49-1c72-4982-a844-72a0f2150127 16.Jan.15 16:16 bp-16b8bbb6-50ac-488f-9b76-e556d2150127 15.Jan.15 09:29 bp-73228909-fa5b-4c28-93bc-fd77a2150127 14.Jan.15 00:17 bp-3e321193-67bb-46a4-b3f2-0e2982150127 12.Jan.15 19:42 bp-f6fa6320-c682-4feb-aa6b-5fb272150127 11.Jan.15 08:13
John99 971 Lösungen 13138 Antworten
Veröffentlicht

Please just provide the actual text commencing bp- of the most recent 3 or 4 reports Crash IDs. The forum changes those to links AFTER you preview and post the reply.

Firefox 5 is quite old, but even Firefox 28 is old and unsupported. You now need to be on Firefox 35.

See also

Please just provide the actual text commencing '''bp-''' of the most recent 3 or 4 reports Crash IDs. The forum changes those to links AFTER you preview and post the reply. Firefox 5 is quite old, but even Firefox 28 is old and '''unsupported'''. You now need to be on Firefox 35. See also * [[Update Firefox to the latest version]] * [[Firefox crashes - asking for support]] *[[Firefox crashes - Troubleshoot, prevent and get help fixing crashes]]
John99 971 Lösungen 13138 Antworten
Veröffentlicht

Hilfreiche Antwort

Thanks for the Crash IDs . We need Crash IDs from the supported version of Firefox.

See also

as linked from my other post.

Thanks for the Crash IDs . We need Crash IDs from the supported version of Firefox. See also * [[Firefox crashes - Troubleshoot, prevent and get help fixing crashes]] as linked from my other post.

Fragesteller

Hi John- The reason I'm on 28 is from 29 on the relocation of the tabs and the layout of the buttons was not, for me, an improvement or a pleasant change (like driving a friend's car-you reach over to turn on the heat and the radio starts blaring because the radio is where the heater should be). As I mentioned earlier, I've been trying other browsers and I've found one that is minimizing the learning curve, but I haven't given up on firefox.

Which leads me to 35, which I had installed a few days ago. I had hoped to get the lack of response to any of my couple hundred crash reports issue sorted before I started with the next issue, because it's off topic for the crash forum, but about 2 days ago a lot of pages started not loading properly- sites like IMDb, Yahoo and Wikipedia started loading as white pages with plain black text and no images displayed. So I reverted back to ff28, and that issue persists, but like I said, one issue at a time, and each in it's place.

So if I can't get support because I'm not willing to relearn the new layout, so be it. But the question remains- why is the crash report soliciting my email address if, over the span of a couple hundred crashes in a year, I get zero communication?

Hi John- The reason I'm on 28 is from 29 on the relocation of the tabs and the layout of the buttons was not, for me, an improvement or a pleasant change (like driving a friend's car-you reach over to turn on the heat and the radio starts blaring because the radio is where the heater should be). As I mentioned earlier, I've been trying other browsers and I've found one that is minimizing the learning curve, but I haven't given up on firefox. Which leads me to 35, which I had installed a few days ago. I had hoped to get the lack of response to any of my couple hundred crash reports issue sorted before I started with the next issue, because it's off topic for the crash forum, but about 2 days ago a lot of pages started not loading properly- sites like IMDb, Yahoo and Wikipedia started loading as white pages with plain black text and no images displayed. So I reverted back to ff28, and that issue persists, but like I said, one issue at a time, and each in it's place. So if I can't get support because I'm not willing to relearn the new layout, so be it. But the question remains- why is the crash report soliciting my email address if, over the span of a couple hundred crashes in a year, I get zero communication?
John99 971 Lösungen 13138 Antworten
Veröffentlicht

Ausgewählte Lösung

The crash report workflow will ask for email addresses, but only very rarely will developers need to contact anyone for further information.

Only the current Release version (& ESR) is supported. Developers will only try to fix issues in the Release version, so there is little or no point in submitting Crash reports from unsupported versions. If you need help and information on crashes you need to submit the crash report AND then report the Crash ID on this forum

AFAIK the crash report submission does send you an email but it is not personalised enough to even link to the correct actual crash report. {inactive} Bug 765296 - [postcrash] Email individual users after a crash

Firefox 29 was a big and controversial change. Related help articles are

Have you considered the possibility of trying to get Firefox to work and customising it to look and behave more like the older version that you like.

The crash report workflow will ask for email addresses, but only very rarely will developers need to contact anyone for further information. Only the current Release version (& ESR) is supported. Developers will only try to fix issues in the Release version, so there is little or no point in submitting Crash reports from unsupported versions. If you need help and information on crashes you need to submit the crash report AND then report the Crash ID on this forum AFAIK the crash report submission does send you an email but it is not personalised enough to even link to the correct actual crash report. <sub>{inactive} Bug 765296 - [postcrash] Email individual users after a crash </sub> Firefox 29 was a big and controversial change. Related help articles are * [[Learn more about the design of the new Firefox]] *[[How to make the new Firefox look like the old Firefox]] Have you considered the possibility of trying to get Firefox to work and customising it to look and behave more like the older version that you like.

Fragesteller

John- Thanks for the links. I have again upgraded to 35.0.1 and enabled automatic updates and spent some time tweaking the appearance (tabs back where they belong is great). Hopefully 35 proves to be a stable platform for me. As far as all the previous crashes go, I guess I'll never know, but it would be beneficial if Mozilla were a little more forthcoming with the steps to handle a crash, as opposed to "Allow Mozilla to contact you--> Restart firefox". For instance, the "bp-" prefix on the reports, and the manual submission of reports. But no, like I said before; over 200 crashes in the last 10-11 months, and never one email back.

So thanks to you and Fred for the time you have given to my problems.

Cheers

John- Thanks for the links. I have again upgraded to 35.0.1 and enabled automatic updates and spent some time tweaking the appearance (tabs back where they belong is great). Hopefully 35 proves to be a stable platform for me. As far as all the previous crashes go, I guess I'll never know, but it would be beneficial if Mozilla were a little more forthcoming with the steps to handle a crash, as opposed to "Allow Mozilla to contact you--> Restart firefox". For instance, the "bp-" prefix on the reports, and the manual submission of reports. But no, like I said before; over 200 crashes in the last 10-11 months, and never one email back. So thanks to you and Fred for the time you have given to my problems. Cheers