Closed Bug 266391 Opened 20 years ago Closed 20 years ago

crash on startup

Categories

(SeaMonkey :: General, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 242769

People

(Reporter: relf, Unassigned)

Details

(Keywords: crash)

Mozilla linux build 2004102606

Talkback ID: TB1568391Q
ld-linux.so.2 + 0x75d5 (0xb7ff15d5)
ld-linux.so.2 + 0x7def (0xb7ff1def)
ld-linux.so.2 + 0xb9b3 (0xb7ff59b3)
ld-linux.so.2 + 0xbbe0 (0xb7ff5be0)
NS_NewTimer()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/
threads/nsTimerImpl.cpp, line 635]
nsRecyclingAllocator::Malloc()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/
xpcom/ds/nsRecyclingAllocator.cpp, line 200]
nsRecyclingAllocatorImpl::Alloc()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/
mozilla/xpcom/ds/nsRecyclingAllocator.cpp, line 386]
nsSegmentedBuffer::AppendNewSegment()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2
-2_Clobber/mozilla/xpcom/io/nsSegmentedBuffer.cpp, line 104]
nsPipe::GetWriteSegment()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/
xpcom/io/nsPipe3.cpp, line 484]
nsPipeOutputStream::WriteSegments()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/
mozilla/xpcom/io/nsPipe3.cpp, line 1072]
nsStreamCopierOB::DoCopy()
nsAStreamCopier::Process()
nsAStreamCopier::HandleContinuationEvent()
PL_HandleEvent()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/xpcom/
threads/plevent.c, line 692]
nsIOThreadPool::ThreadFunc()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/
mozilla/netwerk/base/src/nsIOThreadPool.cpp, line 199]
_pt_root()  [/builds/tinderbox/SeaMonkey-Release/Linux_2.4.2-2_Clobber/mozilla/nsprpub/pr/src/
pthreads/ptthread.c, line 220]
libpthread.so.0 + 0x49b4 (0xb7f049b4)
your stack signature points to bug 242769. Is this a dupe of that report? Does
your browser start the second time?

*** This bug has been marked as a duplicate of 242769 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Max: ld-linux.so is a system library, so it being in the stack really says
nothing about the crash.  the rest of the stack here and in bug 242769 are
completely different...
(In reply to comment #4)
> Max: ld-linux.so is a system library, so it being in the stack really says
> nothing about the crash.  the rest of the stack here and in bug 242769 are
> completely different...

I got Mozilla run when started for the second time, so from user point of view I
see no difference with bug 242769. Though if you see difference in the stack,
feel to reopen this bug. But I cannot be helpful anymore since I cannot
reproduce the crash.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.