Closed Bug 152094 Opened 22 years ago Closed 22 years ago

Random crashes in Mozilla 0.9.9 and 1.0

Categories

(SeaMonkey :: General, defect)

DEC
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: shannon, Assigned: Matti)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux alpha; en-US; rv:0.9.9) Gecko/20020414 Debian/0.9.9-6 BuildID: 20020414 I have experienced random crashes in Mozilla 0.9.9 (debian package, from Woody) and Mozilla 1.0 (built from source, with optimizations for small size) on my Alpha 633 (Ruffian). There appears to be no consistency whatsoever, with respect to web pages or open apps when the crash occurs. X/KDE return no segfault mesages, and I cannot find a core file. If I restart Mozilla and go to the same page that it just crashed on, it works fine. I have not experienced this behavior on my x86 boxes, in Win98 or Debian 2.2 or 3.0 Reproducible: Couldn't Reproduce Steps to Reproduce: Random failure Actual Results: Random Failure Expected Results: Mozilla 1.0 should be stable on this architecture, especially when built from source.
We can't fix this without a stack trace.. We have Talkback on X86 Linux, MAC or win32 to find those random crashes. Could be 64Bit problem or a compiler problem. (with compiler options do you used ?)
I believe the debian package uses the RPM startup script and one of the first things it does is to limit core size to zero. (ulimit -c 0). remove that and you should get core files mozilla 1.0 will not dump core because of bug 148453. If you want a core file with 1.0 (or beyond), you'll have to hack out the signal handlers in nsProfileLock::Lock in nsProfileAccess.cpp (this will leave behind stale lock files whenever you crash, but you'll get core files). beyond that... run Mozilla under gdb. :)
s/with Compiler/which Compiler
there's no reason to expect mozilla to be more stable when you build from source. please attach a stacktrace, this bug is not useful without one.
URL: varies
marking worksforme. I have been running 1.1 branch (on Linux-Alpha) for a while with no major problems.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.