搜尋 Mozilla 技術支援網站

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

Learn More

3.6.7 Crashes

  • 6 回覆
  • 4 有這個問題
  • 7 次檢視
  • 最近回覆由 ffabris

more options

Firefox has started crashing on a frequent basis since 3.6.7. 3.6.6 would crash everyone once in a great while. 3.6.7 is crashing at least twice a day. No pattern. No a particular website, plugin, etc causing it. Including 2 crash reports.

Crash ID(s)

674ef05b-4287-4863-94e6-a4a122100722, c506dc91-f0b1-4bac-8abe-633282100722

Firefox has started crashing on a frequent basis since 3.6.7. 3.6.6 would crash everyone once in a great while. 3.6.7 is crashing at least twice a day. No pattern. No a particular website, plugin, etc causing it. Including 2 crash reports. == Crash ID(s) == 674ef05b-4287-4863-94e6-a4a122100722, c506dc91-f0b1-4bac-8abe-633282100722

所有回覆 (6)

more options

the new version is crashing constantly. i'm surprised that i made it as far as this forum without crashing.

more options

Adding another crash ID. ed3bcf58-807f-4662-9da7-b03bb2100723

more options

I just purchased a new Acer Aspire 7745G laptop with Windows 7 Home Premium 64-bit. The computer has a core i7 Q720 processor and 4 MB RAM. Sometimes FireFox just closes out, even with many tabs open. I use this same version on two Dell P4 machines without any problems. When I restart Firefox, it does not attempt crash recovery.

more options

This should hopefully be resolved as they just (very quickly) released 3.6.8.

more options

I had crashes of 3.6.8 firefox due to using logmein plugin. The story is complicated, but it amazes me how

logmein new plugin is installed in one directory

while

firefox finds an (old) plugin in the other directory.

Then logmein keeps asking me to update plugin.

Amazing!!!

Details here:

http://annoyances-resolved.blogspot.com/2010/08/logmein-plugin-crashes-firefox-demands.html

more options

Copied from https://support.mozilla.com/en-US/questions/747009

OK, I'll do your homework for you. All crashes occur here: caps/src/nsScriptSecurityManager.cpp:2271

Just above that line, a pointer is created and initialized with another one (in the for loop). The new pointer is then dereferenced. But the new pointer is never tested to see if it is NULL. If it is NULL, then the program will crash. So clearly, sometimes it is NULL. This is an elementary programming faux pas; you always check to ensure that pointers are non-NULL before using them.

Now, perhaps you can stop pointing fingers at add-ons and finally fix FF.