LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Desktop (http://www.linuxquestions.org/questions/linux-desktop-74/)
-   -   Segmentation fault in Firefox and chrome (http://www.linuxquestions.org/questions/linux-desktop-74/segmentation-fault-in-firefox-and-chrome-4175482101/)

decenter 10-25-2013 05:14 AM

Segmentation fault in Firefox and chrome
 
Hello,

My desktop specs:

OS : Linux Deepin 2013

Arch : X86_64

RAM : 4096 MiB

Recently when I open Firefox and Google chrome, I get those crashed with the error Segmentation fault. Even when I leave the browser open with several websites, suddenly it crashes with segmentation fault.

A note: Once I was unable to launch Google chrome browser. So I entered in to Terminal and tried to run from there. All I got was Segmentation fault. Then I rebooted the machine and I can launch Google chrome successfully and this time it didn't give any segmentation fault. So it happens at random times but very often.

Also, I can launch any other applications such as Terminal, Libreoffice, Nemo without any crash. Only with these browsers.

Steps I followed to debug the issue:

1. Disabled all the addons and ran firefox in safe mode.

2. Ran command : strace firefox to trace the issue and it gave only Segmentation fault.

3. Ran Memtest86+ to test the RAM. My RAM chip passed the test with no errors.

This issue is not reproducible, but it occurs at random times but very often.


Yet, I get Segmentation fault.

I couldn't get in to work with these segmentation fault errors and I lose my precious time and the work I done when the browser crashes. Please help me on this issue.

Thanks.

For added information on the issue please see post #17.

isamuede 10-25-2013 02:01 PM

I used to have errors like this, check if you have correctly installed the video drivers (yes, its odd but installing the right ones did the job)

decenter 10-25-2013 08:45 PM

Segmentation fault in Firefox and chrome
 
I have the default video drivers installed. Also I have the latest system updates installed.

decenter 10-29-2013 07:30 AM

Any help on this? I'm keep getting irritated due to this segmentation fault. I even re-installed OS and this time I installed Ubuntu 12.04.3 LTS and the issue persists. I think its hardware issue than software issue. Whats your idea? How to debug it?

pan64 10-29-2013 08:20 AM

if only firefox (and chrome) crashed it could be hardly a hardware issue. You may try to analyze coredump to get some more info about it.

decenter 10-29-2013 09:28 AM

Quote:

Originally Posted by pan64 (Post 5054474)
if only firefox (and chrome) crashed it could be hardly a hardware issue. You may try to analyze coredump to get some more info about it.

Now I found that even other applications are crashing due to segmentation fault. I couldn't open synaptic due to segmentation fault. Only after reboot I could access it. Even if reinstalled another OS and it also give the same error means, I think it must be hardware issue.

How to get core dump?

pan64 10-29-2013 09:32 AM

Usually that will automatically created in case of segfault.
You may try memtest to check memory.

decenter 10-29-2013 11:58 AM

I already ran memtest and the RAM chip passed the test. I will run it again for you and will report.

John VV 10-29-2013 02:03 PM

HOW did you install firefox ?
it is already installed by default on on the lts ubuntu it "should" be the OLD lts firefox 17.0.7 or .0.8 or the current 17.0.9

or

did you manually put firefox 24( now 25) on the machine

decenter 10-29-2013 11:12 PM

Quote:

Originally Posted by John VV (Post 5054687)
HOW did you install firefox ?
it is already installed by default on on the lts ubuntu it "should" be the OLD lts firefox 17.0.7 or .0.8 or the current 17.0.9

or

did you manually put firefox 24( now 25) on the machine

Firefox version 23.0 was present in Ubuntu 12.04.3 LTS and I just updated using synaptic.

Btw, now most of the apps in the system gets crashed due to SIGSEGV . So I guess it is a hardware issue than software issue.

John VV 10-30-2013 12:08 AM

a bad drive is a likely issue

if many things can not find libs that ARE installed then it could be bad sectors
-- but that is a guess

what is in the system logs ?
/var/log/????

pan64 10-30-2013 01:27 AM

about segfaults. You may try to collect coredumps and check them. There are two possible cases: 1. you will find similar coredumps, the segfault occurred on the same place. It means possible driver problem. 2. you will not find similar dumps, the segfaults occurred on different places, in different libs. It means possible hardware issue.

decenter 10-30-2013 03:34 AM

Quote:

Originally Posted by pan64 (Post 5054969)
about segfaults. You may try to collect coredumps and check them. There are two possible cases: 1. you will find similar coredumps, the segfault occurred on the same place. It means possible driver problem. 2. you will not find similar dumps, the segfaults occurred on different places, in different libs. It means possible hardware issue.

My syslog says:

cat syslog.1 | grep segfault
Oct 29 17:18:36 decenter-desktop kernel: [ 94.069845] check-new-relea[1790]: segfault at 0 ip 000000000046629f sp 00007fff625e2d10 error 4 in python2.7[400000+272000]
Oct 29 17:19:56 decenter-desktop kernel: [ 173.222342] dbus-daemon[735]: segfault at 7ff1be0c9674 ip 00007ff1bcd52aee sp 00007fff717e3d30 error 4 in dbus-daemon[7ff1bcd3d000+62000]
Oct 29 17:20:52 decenter-desktop kernel: [ 229.660941] colord[4000]: segfault at 2490ad0 ip 00007f79846ad8d2 sp 00007fffc90650c8 error 4 in ld-2.15.so[7f7984695000+22000]
Oct 29 17:21:31 decenter-desktop kernel: [ 268.168442] nm-applet[1488]: segfault at 8 ip 00007f0727cac5e1 sp 00007fff11ef0890 error 4 in libnm-glib.so.4.3.0[7f0727c9b000+35000]
Oct 29 12:23:49 decenter-desktop kernel: [ 34.611006] xdg-user-dirs-g[1694]: segfault at 7f48f26e5e00 ip 00007f48f6df06a2 sp 00007fff5567fbf0 error 4 in ld-2.15.so[7f48f6de2000+22000]
Oct 29 15:35:26 decenter-desktop kernel: [11530.834847] plugin-containe[13653]: segfault at 0 ip 00007f4383aa2fdf sp 00007fff30eeade0 error 6 in libmozalloc.so[7f4383aa2000+2000]
Oct 29 16:52:14 decenter-desktop kernel: [16139.154580] indicator-senso[17859]: segfault at 0 ip 000000000040a2ac sp 00007fff55ef3b00 error 4 in indicator-sensors[400000+18000]
Oct 29 17:00:35 decenter-desktop kernel: [ 408.833130] indicator-senso[2727]: segfault at 0 ip 000000000040a2ac sp 00007fff54608810 error 4 in indicator-sensors[400000+18000]
Oct 30 09:40:22 decenter-desktop kernel: [ 130.250024] indicator-multi[1707]: segfault at 7f5700000001 ip 00007f57e3fd4e0a sp 00007fff862a8ae0 error 4 in libglib-2.0.so.0.3200.4[7f57e3f74000+f2000]
Oct 30 09:44:43 decenter-desktop kernel: [ 391.665292] chrome[2587]: segfault at 7fc272ce7399 ip 00007fc272ce7410 sp 00007fff1e5e8758 error 7 in chrome[7fc270f24000+57c8000]
Oct 30 09:44:48 decenter-desktop kernel: [ 396.096043] chrome[2469]: segfault at 39 ip 00007f421ca8d150 sp 00007fff10024c98 error 6 in chrome[7f421b9b4000+57c8000]
Oct 30 09:48:20 decenter-desktop kernel: [ 608.359979] chrome[2837]: segfault at 8 ip 00007f2d44768c1d sp 00007fff06d3f548 error 4 in chrome[7f2d427fb000+57c8000]

pan64 10-30-2013 03:57 AM

so it looks like a hw error: RAM, HDD or ?. You can check smart info too.

decenter 10-30-2013 07:15 AM

Quote:

Originally Posted by pan64 (Post 5055024)
so it looks like a hw error: RAM, HDD or ?. You can check smart info too.


Ok. I checked the RAM again using Memtest86+ but no errors came. It is same with HDD (no errors). Still I get segmentation fault. I do not know what causes this issue.


All times are GMT -5. The time now is 01:35 AM.