Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Firefox crashes

  • 25 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: LuminaryCrush

more options

I wish I knew why Firefox has been crashing, but even in Safe Mode it dies. Here's what I do know:

1) Firefox was running fine in Fedora 17. Very rarely a crash even with 30 windows and 100+ tabs on multiple desktops.

2) I upgraded (as in: new install, but same home directory) from Fedora 17 to Fedora 20. No new hardware. Constant crashes - sometimes multiple times per hour. Sometimes multiple times per minute. Sometimes, crashing immediately on 'restart' of session while opening all my tabs back up & I have to do this a few times to get it working... usually, once it's up, it stays running for an hour or two.

3) Reduced windows to 12-15, and tabs to ~30. No effect.

4) Tried creating a new profile; tried different desktop environment (Cinnamon vs Gnome); tried uninstalling Flash plugin, other plugins, and then tried Safe Mode. Crash, crash crash.

I'm kind of at my wit's end. Fedora 20 is updated with latest packages. I am using the Nvidia proprietary drivers, but it crashes even in "Safe Mode", so hardware accel shouldn't be the cause.

I can run memtest86+ (which could take quite a while on a 16G RAM machine), but it would be quite a coincidence that I would have a memory failure right at the time I upgraded to Fedora 20, would it not?

I wish I knew why Firefox has been crashing, but even in Safe Mode it dies. Here's what I do know: 1) Firefox was running fine in Fedora 17. Very rarely a crash even with 30 windows and 100+ tabs on multiple desktops. 2) I upgraded (as in: new install, but same home directory) from Fedora 17 to Fedora 20. No new hardware. Constant crashes - sometimes multiple times per hour. Sometimes multiple times per minute. Sometimes, crashing immediately on 'restart' of session while opening all my tabs back up & I have to do this a few times to get it working... usually, once it's up, it stays running for an hour or two. 3) Reduced windows to 12-15, and tabs to ~30. No effect. 4) Tried creating a new profile; tried different desktop environment (Cinnamon vs Gnome); tried uninstalling Flash plugin, other plugins, and then tried Safe Mode. Crash, crash crash. I'm kind of at my wit's end. Fedora 20 is updated with latest packages. I am using the Nvidia proprietary drivers, but it crashes even in "Safe Mode", so hardware accel shouldn't be the cause. I can run memtest86+ (which could take quite a while on a 16G RAM machine), but it would be quite a coincidence that I would have a memory failure right at the time I upgraded to Fedora 20, would it not?

모든 댓글 (5)

more options

If you have the default 32-bit Firefox version then you need 32 bit versions of plugins and Firefox won't look in /usr/lib64 where the 64 bit versions reside.

more options

Your crash problem is not restricted to the googletalk plugin. It may be another plugin's fault. I would cut and paste all the plugins found in the firefox plugin folder to another folder then try starting Firefox to see what happens. Also what were the results of your strace? You can post them here.

more options

$ file firefox-bin firefox-bin: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.18, BuildID[sha1]=ad1a32d999e65c88921007f34660c55e4913fe8d, stripped

more options

Just out of curiosity, shouldn't safe mode ignore plugins? I will move the files out and try that but if safe mode still loads the libraries it's not really too useful. I've already moved off the ~/.mozilla/plugins directory.

The strace is really big...19G. Is there a way to get to useful information? Also, casually browsing the file contents I see it could contain information of a security concern.

more options

I moved off the plugins directory in /usr/lib64/mozilla and ~/.mozilla and I still get crashes with FF33. The runtime lasted a couple of hours before implosion.

Something in combination with Fedora 20 and FF seems to be the issue as this does not occur in FC17.

  1. 1
  2. 2