GNOME Bugzilla – Bug 376826
crash in Evolution: It was running in the ba...
Last modified: 2007-04-12 21:39:33 UTC
What were you doing when the application crashed? It was running in the background: it had been open for a few hours now. I was editing source code in the NetBeans IDE. If the stack traces are not sufficient I'm afraid I'll need help with exactly what symbols to install. I have reported other bugs and gotten the request for more symbols; and I have installed all the packages specifically mentioned. I won't know what else to install unless someone tells me specifically. Thanks in any case. Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: -1150054400 vsize: 0 resident: -1150054400 share: 0 rss: 523837440 rss_rlim: 0 CPU usage: start_time: 1163878790 rtime: 0 utime: 6430 stime: 0 cutime:4895 cstime: 0 timeout: 1535 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 -1233381712 (LWP 4931)] [New Thread -1358955616 (LWP 4993)] [New Thread -1322783840 (LWP 4981)] [New Thread -1300653152 (LWP 4958)] [New Thread -1291846752 (LWP 4954)] [New Thread -1283454048 (LWP 4953)] [New Thread -1260524640 (LWP 4947)] [New Thread -1252095072 (LWP 4944)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 87576
Thread 8 (Thread -1252095072 (LWP 4944))
*** Bug 378587 has been marked as a duplicate of this bug. ***
*** Bug 378664 has been marked as a duplicate of this bug. ***
*** Bug 396291 has been marked as a duplicate of this bug. ***
Hi. At the request of Christian Kirbach, I have been trying to re-create bug id 366448. I just managed to see Evo crash in the background again. The dupfinder tells me this new stack trace matches this bug. So, I will attach the trace from this new crash here. I will also attach it to bug 366448 -- the dupfinder did not say that this was a duplicate of 366448, but it still may be so... I don't know obviously. But I have installed several debug packages since that time so may be the search is not 100% accurate. Anyway. here comes the new trace. Thanks.
Created attachment 81611 [details] Stach trace of crash in background.
Created attachment 81975 [details] Stack traces from Bug Buddy. Another crash. I do not claim to know how to read this right, but the actual memory usage numbers showing in my System Monitor are like so: Virtual Memory 2.9GiB, Resident 500.5MiB, Writable 486.1Mib, Shared 13.0MiB, X Server 528.6KiB, and just "Memory" 486.6MiB. I point it out because Eveo definitely has a leak: it swaps out the whole 3GiB swap space eventually. It's possible that it crashes right at that point, but I don't know. Another clue might be related to the networking stack: I perceive that Evo crashes sooner if I start Liferea during the same session. I might be wrong since Evo crashes absolutely all the time, but it seemed that if I ran Liferea it went sooner. You can feel all the swapping going on for sure: the curser slows down and jumps all over the monitor, and you can't switch back and forth between apps anymore. And sometimes it does not take long at all to go down. It might also go faster when I open a new message window and compose some outgoing message. This crash did not take long (and all 3 gigs of swap have been chewed up already.) Thanks again......
*** Bug 418309 has been marked as a duplicate of this bug. ***
*** Bug 419460 has been marked as a duplicate of this bug. ***
*** Bug 420853 has been marked as a duplicate of this bug. ***
*** Bug 424771 has been marked as a duplicate of this bug. ***
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of 352284 ***