GNOME Bugzilla – Bug 366448
crash in Evolution: It was runnin gin the ba...
Last modified: 2008-02-25 17:14:26 UTC
What were you doing when the application crashed? It was runnin gin the background when I had the Add/Remove Programs dialog open: I had installed 2 applications ther; and now I selected 2 more and when I hit the "Apply" (Install) buttun, Evolution crashed in the background. It's status bar indicates it was "Fetching Mail (...)" when it crashed... Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: -1258446848 vsize: 0 resident: -1258446848 share: 0 rss: 612601856 rss_rlim: 0 CPU usage: start_time: 1162059384 rtime: 0 utime: 28495 stime: 0 cutime:26689 cstime: 0 timeout: 1806 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1232484688 (LWP 7833)] [New Thread -1614808160 (LWP 7961)] [New Thread -1551397984 (LWP 7867)] [New Thread -1309926496 (LWP 7858)] [New Thread -1286616160 (LWP 7854)] [New Thread -1261438048 (LWP 7853)] [New Thread -1278223456 (LWP 7849)] [New Thread -1269830752 (LWP 7844)] [New Thread -1251193952 (LWP 7842)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 79411
Thread 9 (Thread -1251193952 (LWP 7842))
Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Hi. It crashed again: different circumstances this time, but it crashes so often that it's likely this is a related stack trace. I'll post it for you. This time I was viewing messages in the Inbox, and when I selected one in the list, Evo crashed. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 283037696 vsize: 0 resident: 283037696 share: 0 rss: 129150976 rss_rlim: 0 CPU usage: start_time: 1169092771 rtime: 0 utime: 2388 stime: 0 cutime:2157 cstime: 0 timeout: 231 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232591184 (LWP 24844)] [New Thread -1463026784 (LWP 25052)] [New Thread -1269826656 (LWP 24885)] [New Thread -1328546912 (LWP 24875)] [New Thread -1278219360 (LWP 24873)] [New Thread -1295041632 (LWP 24872)] [New Thread -1303434336 (LWP 24864)] [New Thread -1286612064 (LWP 24861)] [New Thread -1260360800 (LWP 24858)] [New Thread -1251968096 (LWP 24857)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 103160
Thread 1 (Thread -1232591184 (LWP 24844))
By the way: I did locate a couple more debug packages that seemed relevant, and installed them. I've viewed the "help" page about which debug packages to install, and I've tried to locate everything mentioned -- and I think I have. But, it's a bit hard to tell since the package names are varied. So if there's something you can tell me specifically to install I'll do that. Thanks anyway!
Hi. I got another crash: it crashed while it was starting up. Here's another stack trace: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 128528384 vsize: 0 resident: 128528384 share: 0 rss: 28479488 rss_rlim: 0 CPU usage: start_time: 1169837394 rtime: 0 utime: 183 stime: 0 cutime:171 cstime: 0 timeout: 12 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232595280 (LWP 10364)] [New Thread -1280312416 (LWP 10382)] [New Thread -1297097824 (LWP 10381)] [New Thread -1305490528 (LWP 10378)] [New Thread -1288705120 (LWP 10375)] [New Thread -1261438048 (LWP 10372)] [New Thread -1251972192 (LWP 10371)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 105486
Thread 1 (Thread -1232595280 (LWP 10364))
last trace is bug 363576 but all traces differ, so that is 3 different problems.. we still miss a trace with debug symbols of the original trace
Crashed again: a bit more typical this time: I had launched it, it checks mail automatically, I deleted messages from the on box, then I just closed the application and it crashes at that point. This is how it crashes 75% of the time when it does (and it does crash a lot). So here's a trace. Thanks. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 186740736 vsize: 0 resident: 186740736 share: 0 rss: 69988352 rss_rlim: 0 CPU usage: start_time: 1170090857 rtime: 0 utime: 879 stime: 0 cutime:779 cstime: 0 timeout: 100 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution-2.8' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread -1232578896 (LWP 5088)] [New Thread -1342178400 (LWP 5175)] [New Thread -1303450720 (LWP 5156)] [New Thread -1326797920 (LWP 5127)] [New Thread -1269826656 (LWP 5117)] [New Thread -1286665312 (LWP 5114)] [New Thread -1295058016 (LWP 5107)] [New Thread -1278219360 (LWP 5100)] [New Thread -1260348512 (LWP 5099)] [New Thread -1251955808 (LWP 5098)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 106328
Thread 1 (Thread -1232578896 (LWP 5088))
phew .. last trace is unique, however it is not the original problem nonetheless, excellent trace, I filed it as Bug 402207 can you please retry to create the *original* crash, and append the traces as *attachments* to this document, increasing readability. thank you.
I'll do as you've suggested. If I leave it running in the background there's a good chance it should crash again. It still crashes often as I've said, but I haven't seen it crash while just sitting in the background for a while. I don't know if it has anything to do with any of the patches I have seen installed recently (via automatic updates); or maybe I have been avoiding it since I tend to quit it because of the crashes. I bet it will go again: it still seems to be chewing up all the ram after running for a while. Thanks.
Gotcha! I had Evo running for quite a while, and I was doing other things. At some point I minimized it, and seemingly immediately it crashed. I'll attach the trace. Hopefully it is the same condition. Thanks.
Created attachment 81477 [details] Trace of a crash when minimized.
last trace matches Bug 381378 Steven, can you please try to reproduce the original crash? copy comnpletely the trace of a crash and paste it into http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi if the utility detects that the pasted traces matches this bug (bug 366448), then please attach the trace to this report. thank you. if you have any questions, feel free to mail me personally.
(In reply to comment #11) > last trace matches Bug 381378 > > Steven, can you please try to reproduce the original crash? > > copy comnpletely the trace of a crash and paste it into > http://bugzilla.gnome.org/dupfinder/simple-dup-finder.cgi > > if the utility detects that the pasted traces matches this bug (bug 366448), > then please attach the trace to this report. thank you. > if you have any questions, feel free to mail me personally. > Hi. I got a crash in the background. The dupfinder does not say it matches this bug; however, it does say it matches bug 376826, which is I think this same crash: at least, it was a crash in the background that appeared for all intents and purposes on my machi ne to be the same behavior. I attached this trace to that bug, but I'll attach it here too. I have installed several debug packages since reporting that other bug, so maybe the trace just looks different to the dupfinder... Please feel free to let me know if this was useful or not; I'll keep trying. Thanks.
Created attachment 81612 [details] Trace of a crash in background - January 2007.
Hi. I just got another crash: this time I was switching Evo into the background -- err. actually I launched Firefox and during the launch sequence Evo crashed. The dupfinder does not say this trace matches this bug or bug 376826, but it does say that it matches bug 330728 so I attached the traces to that bug. In case it's helpful, you can see them there. Thanks again.
Created attachment 83051 [details] Trace of a crash when viewing mail in the inbox. Hi. Evolution crashed on me while I was viewing inbox messages. The dupfinder says this trace is a duplicate of this bug, so here's an attachment of the traces. I was in the process of composing a draft message. Evolution checked mail in the background and played the notification sound. I clicked "Save Draft" on the message I was writing and the switched to the inbox. I selected one of the messages and Evolution crashed. This is the trace from Bug Buddy. Then, I re-started Evolution and it crashed right away on startup. I will attach that trace as well following this one. Thanks again, Steven Coco.
Created attachment 83052 [details] Trace of a crash restarting after crashing when viewing mail in the inbox. As mentioned in my previous attachment, this is a trace from Bug Buddy of Evolution crashing right at startup after re-starting from the last crash.
Created attachment 84610 [details] BugBuddy traces: crashed while quitting. Evo crashed again. This time I was quitting. The dupfinder says it duplicates this bug. Attached are the traces.
Created attachment 84985 [details] Bug Buddy Output From Evolution Crash While Quitting Evo crashed again on me while quitting. Though the dupfinder does not indicate this matches, this is on this same machine, so it may be related. Here's the traces: I have installed dozens of debug packages since the last report. (I searched the package manager for "dbg" and installed every package that would install without requiring new dependencies!) Thanks!
hmm still not the original crash, but a good trace I have no idea what to do now; maybe a developer will hop by. You did some software upgrades while the first crash happened; I have the feeling that you replaced some of Evolution's dependency libraries which caused a crash.
Phew, Actually this bug report is too messy to work with it. Searching is a PITA and this bug shows up pretty often in s-d-f ;-) So my suggestion is to file a bug for each pretty trace (if there are any left...) and then close this one as INVALID.
I agree with Tobias, even most of the crashers has been fixed already. The initial crash is because of low memory I guess, it probably failed to allocate a bit more.
Closing as per comment #20 and comment #21.