Closed
Bug 476657
Opened 16 years ago
Closed 15 years ago
Thunderbird Crashing with Lightning
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: eblix08, Unassigned)
Details
(Keywords: crash, Whiteboard: [has stacktrace])
Attachments
(1 file)
580.40 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121622 Fedora/3.0.5-1.fc10 Firefox/3.0.5
Build Identifier: thunderbird.i386 2.0.0.19-1.fc10 thunderbird-lightning.i386 0.9-3.fc10
Over the past few weeks Thunderbird started crashing at different times with no apparent common trigger.
Thunderbird was automatically updated as follows:
Jan 14 09:21:50 Installed: thunderbird.i386 2.0.0.19-1.fc10
Jan 14 09:54:43 Installed: thunderbird-lightning.i386 0.9-3.fc10
Reproducible: Sometimes
Steps to Reproduce:
1. Run Thunderbird.
2. Continue working, at some point Thunderbird will crash.
3. Restart Thunderbird, hope it doesn't crash again.
Actual Results:
Crashed
Expected Results:
No crash
gecko-bugreport.txt will be attached once this has been submitted.
Comment 2•16 years ago
|
||
We can't use the Gecko Bugreport, we need a stacktrace with symbols.
Either from an original Mozilla.org build with talkback or from your fc.10 build in GDB with debug symbols installed.
I have not used talkback or GDB before. Talkback does not appear to be installed so I tried to grab what you need from GDB. I GDB two times, is this what you are looking for?
(gdb) backtrace
#0 0x009e7416 in __kernel_vsyscall ()
#1 0x007e4638 in send () from /lib/libpthread.so.0
#2 0x06f876ce in ?? () from /lib/libnspr4.so
#3 0x06feb11c in ?? () from /lib/libssl3.so
#4 0x06fdb854 in ?? () from /lib/libssl3.so
#5 0x06fdbd26 in ?? () from /lib/libssl3.so
#6 0x06feee62 in ?? () from /lib/libssl3.so
#7 0x06ff3877 in ?? () from /lib/libssl3.so
#8 0x022550e6 in nsNSSSocketInfo::CloseSocketAndDestroy (this=0xb32db888) at nsNSSIOLayer.cpp:1039
#9 0x0224677e in nsSSLThread::requestClose (si=0xb32db888) at nsSSLThread.cpp:425
#10 0x022526fb in nsSSLIOLayerClose (fd=0xb1a9b268) at nsNSSIOLayer.cpp:1024
#11 0x06f6c201 in PR_Close () from /lib/libnspr4.so
#12 0x02aede76 in nsSocketTransport::ReleaseFD_Locked (this=0xb32d8fb8, fd=0xb1a9b268) at nsSocketTransport2.cpp:1347
#13 0x02aee72e in nsSocketTransport::OnSocketDetached (this=0xb32d8fb8, fd=0xb1a9b268) at nsSocketTransport2.cpp:1569
#14 0x02af1265 in nsSocketTransportService::DetachSocket (this=0x8114fe8, sock=0x811503c) at nsSocketTransportService2.cpp:193
#15 0x02af1d1a in nsSocketTransportService::Run (this=0x8114fe8) at nsSocketTransportService2.cpp:615
#16 0x0037dbfb in nsThread::Main (arg=0x81023c0) at nsThread.cpp:118
#17 0x06f8a0d1 in ?? () from /lib/libnspr4.so
#18 0x007dd51f in start_thread () from /lib/libpthread.so.0
#19 0x0071304e in clone () from /lib/libc.so.6
(gdb)
(gdb) backtrace
#0 0x07310b8f in event_processor_callback (source=0xae8416a8, condition=G_IO_IN, data=0xae864660) at nsAppShell.cpp:67
#1 0x009c734d in g_io_unix_dispatch (source=0xae700858, callback=0x7310b7c <event_processor_callback>, user_data=0xae864660) at giounix.c:162
#2 0x00990238 in g_main_dispatch () at gmain.c:2144
#3 IA__g_main_context_dispatch (context=0x8083660) at gmain.c:2697
#4 0x009938e3 in g_main_context_iterate (context=0x8083660, block=1, dispatch=1, self=0x8063890) at gmain.c:2778
#5 0x00993e02 in IA__g_main_loop_run (loop=0x8572590) at gmain.c:2986
#6 0x063e2959 in IA__gtk_main () at gtkmain.c:1200
#7 0x073110d9 in nsAppShell::Run (this=0x8224da0) at nsAppShell.cpp:139
#8 0x019e9d40 in nsAppStartup::Run (this=0x8224d60) at nsAppStartup.cpp:151
#9 0x0804f706 in XRE_main (argc=2, argv=0xbffff894, aAppData=0x8060018) at nsAppRunner.cpp:2817
#10 0x0804abe0 in main (argc=1, argv=0xa3b6a0) at nsMailApp.cpp:62
(gdb) quit
Updated•16 years ago
|
Summary: Thunderbird Crashing → Thunderbird Crashing with Lightning
Version: unspecified → 2.0
Comment 4•15 years ago
|
||
eblix08, do you still see this crash? without lightning?
Whiteboard: [has stacktrace]
I have not seen this crash is quite some time. I am currently running a older Fedora 10 which needs to be upgraded before I would consider researching this further. I am considering this resolved.
Thanks.
Eric
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•