搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Frequent crashes after updating to version 48.0.1

  • 11 回覆
  • 3 有這個問題
  • 35 次檢視
  • 最近回覆由 philipp

more options

Hi

I am using a Windows 10 Pc. FF updated to version 48.0.1 and it is crashing like 6-7 times in 5 minutes. After the update I did not install any plugin or addon. Windows, Drivers etc. everything is updated. I don't have the time to test it in safe mode, as I am busy with some stuff. Any help?

Thanks

所有回覆 (11)

more options

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.

more options

philipp said

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.

Submitted Crash Reports

No crash reports have been submitted.

Any way I can generate a crash report?

more options

do you get a Mozilla Crash Reporter window once firefox crashes? if not, then things might be much more difficult to troubleshoot unfortunately. could you describe the crashing in as much detail as possible (are there any other error messages, is the firefox window just disappearing...)?

more options

philipp said

do you get a Mozilla Crash Reporter window once firefox crashes? if not, then things might be much more difficult to troubleshoot unfortunately. could you describe the crashing in as much detail as possible (are there any other error messages, is the firefox window just disappearing...)?

Yes, I do get the Mozilla Crash Reporter window but I do not select tell Mozilla about it as I didn't knew what info it might share. Crashing just happens all of a sudden, the FF window disappears and the crash reporter window is there. That's pretty much about it.

more options

please DO submit the crash report to mozilla. you can just leave the comment section empty - the important thing that gets submitted are the technical details about the state of the application at the time of the crash. after you have done that, please go back to my first answer and dig up the id of the newly generated crash report.

more options

philipp said

please DO submit the crash report to mozilla. you can just leave the comment section empty - the important thing that gets submitted are the technical details about the state of the application at the time of the crash. after you have done that, please go back to my first answer and dig up the id of the newly generated crash report.

Will do that. Hope it doesn't send any private info.

more options

a crash report might contain the state of the pc memory at the time of the crash and therefore private information - access to that part of the crash report is restricted to a small sample of mozilla engineers though.

this is what the firefox privacy policy says about it:

You have the option to send Mozilla a crash report after Firefox crashes. This report contains technical information for us to improve Firefox including why Firefox crashed, the active URL at time of crash, and the state of computer memory during the crash. The crash report we receive may include personal information. We make portions of crash reports available publicly at https://crash-stats.mozilla.com/). Before publicly posting crash reports, we take steps to automatically redact personal information. We do not redact anything you may write in the comments box.

https://www.mozilla.org/en-US/privacy/firefox/

more options

philipp said

a crash report might contain the state of the pc memory at the time of the crash and therefore private information - access to that part of the crash report is restricted to a small sample of mozilla engineers though. this is what the firefox privacy policy says about it:
You have the option to send Mozilla a crash report after Firefox crashes. This report contains technical information for us to improve Firefox including why Firefox crashed, the active URL at time of crash, and the state of computer memory during the crash. The crash report we receive may include personal information. We make portions of crash reports available publicly at https://crash-stats.mozilla.com/). Before publicly posting crash reports, we take steps to automatically redact personal information. We do not redact anything you may write in the comments box.

https://www.mozilla.org/en-US/privacy/firefox/

bp-720a0603-12e0-4bf6-a15b-5f38e2160820

https://crash-stats.mozilla.com/report/index/720a0603-12e0-4bf6-a15b-5f38e2160820

Looks like I have some malwares as seen in the modules section( source- https://support.mozilla.org/en-US/kb/helping-crashes) but some of those highlighted files do have a version etc. So, what's going on here?

I did install Anti-Porn software by a Chinese company Tueagles few days back, that might be causing this. I have uninstalled this software because I wasn't able to find this flt32.dll file anywhere in the said location- http://www.ifixerror.com/ffiles/128814/flt32-dll-error-how-to-remove-it.html

由 becool773 於 修改

more options

thanks, so yes the crash seems to be directly triggered by the flt32.dll library related to the tuEagles filtering software that is hooking into the firefox process - so removing that will hopefully solve the crashing issue.

your modules list looks quite inconspicuous and doesn't suggest anything malicious going on, so you don't need to worry about that (mozilla just doesn't have any further information about the few entries marked in red available to further debug crashes occurring in their codepath).

more options

philipp said

thanks, so yes the crash seems to be directly triggered by the flt32.dll library related to the tuEagles filtering software that is hooking into the firefox process - so removing that will hopefully solve the crashing issue. your modules list looks quite inconspicuous and doesn't suggest anything malicious going on, so you don't need to worry about that (mozilla just doesn't have any further information about the few entries marked in red available to further debug crashes occurring in their codepath).

Few queries- 1. I really need that Anti-Porn or some kinda similar software to block some sites for the kids, a software which should not mess up with FF or some other software. Any recommendations?

2. Regarding those other entries marked in red in modules, if Mozilla doesn't have further info about them, then why are those marked in red?

more options

1. for an unobstrusive solution you could try setting up your router or computer with the opendns family safe dns server which should basically: https://www.opendns.com/setupguide/?url=familyshield (a dns server is the "telephone book" of the internet, and in this case it would tell the pc that the address isn't known in case a known adult site is accessed).

2. not sure how techical i can become here, but marked in red is basically meaning that no debug symbols are available to us in regards to this module (https://en.wikipedia.org/wiki/Debug_symbol). in the case of a crash there it's not possible to know in which exact function of the module the crash was occurring...