RE: [SLE] Mozilla crashes with segmentation fault
-----Original Message----- From: Darryl Gregorash [mailto:raven@accesscomm.ca] Sent: Monday, September 12, 2005 1:43 PM To: suse-linux-e@suse.com Subject: Re: [SLE] Mozilla crashes with segmentation fault
On 09/12/2005 10:40 AM, Lawrence Bowie wrote:
(OK, now I figured out how to get that reply header format -- now to figure out how to put the original timestamp in there, rather than my own local time. Any hints, anyone? User pref "mailnews.display.original_date" is set as "true".)
How about any other dot files that may have been preserved?
Have you tried moving .mozilla to a different name and allowing it to start clean? This will eliminate it being your dot files. :)
I have been through this recently and the dot file were the culprit as well as other libraries.
Dude, every time I install SuSE, mozilla "starts clean" the very first time I use it. I found a reference on suseforums.com suggesting the same thing, and it didn't work for that person. I fail to see what good it would do to replace one directory with another of the same name, containing precisely the same files, anyway. This seems like replacing the air in your car's tires in the hope it will get rid of a nasty engine knock.
The vast majority of crashes that I've seen in Firefox have been a result of corrupt files in the profile. This is true across platforms: linux, macosx, and windows. If you've clean installed and are seeing the same issues -- and almost everyone else isn't, apparently -- it might actually be time to check your system for faults. Mozilla is a very active program, and it might be that you've got a bad piece of RAM somewhere that Mozilla happens to be the program hitting.
On 09/12/2005 11:46 AM, Marlier, Ian wrote:
<snip> The vast majority of crashes that I've seen in Firefox have been a result of corrupt files in the profile. This is true across platforms: linux, macosx, and windows.
If you've clean installed and are seeing the same issues -- and almost everyone else isn't, apparently -- it might actually be time to check your system for faults. Mozilla is a very active program, and it might be that you've got a bad piece of RAM somewhere that Mozilla happens to be the program hitting. I run a 1-pass memtest every time I upgrade the installation, the most recent one 5 weeks ago. Just so there would be no misunderstanding, I just ran another one -- 5 passes. There is no memory error.
There are enough ongoing reports of segfaults, dating from 1998 until now, that I would not be so sure this is a rare problem.
participants (2)
-
Darryl Gregorash
-
Marlier, Ian