GNOME Bugzilla – Bug 361346
crash in Evolution: Closing evolution
Last modified: 2008-07-11 11:42:25 UTC
What were you doing when the application crashed? Closing evolution Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 1747079168 vsize: 0 resident: 1747079168 share: 0 rss: 411848704 rss_rlim: 0 CPU usage: start_time: 1160542519 rtime: 0 utime: 2358 stime: 0 cutime:1834 cstime: 0 timeout: 524 it_real_value: 0 frequency: 628 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 -1232734544 (LWP 14486)] [New Thread -1856689248 (LWP 14940)] [New Thread -2043696224 (LWP 14933)] [New Thread -1901376608 (LWP 14714)] [New Thread -1391146080 (LWP 14540)] [New Thread -1286530144 (LWP 14512)] [New Thread -1295725664 (LWP 14503)] [New Thread -1278100576 (LWP 14501)] [New Thread -1269707872 (LWP 14498)] (no debugging symbols found) 0xffffe410 in __kernel_vsyscall ()
+ Trace 75744
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
Every time Evolution crashes I send the bug buddy report. Now I have this report numbers: 361205, 361232, 361296, 361309 & 361346 (one day use). Should I stop sendig this reports? I am installing the evolution-dbg package now, in which report number should I fill the results in case of a new crash?
This morning, after 5 minutes running, Evolution was "eating" 420 Mb of my system RAM. When I closed, it crashes (new report ). This is the report created by bug buddy, after I installed the evolution-dbg package (I hope it helps): *** Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: -2038837248 vsize: 0 resident: -2038837248 share: 0 rss: 498294784 rss_rlim: 0 CPU usage: start_time: 1160572412 rtime: 0 utime: 3090 stime: 0 cutime:2378 cstime: 0 timeout: 712 it_real_value: 0 frequency: 4445 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 -1232443728 (LWP 7708)] [New Thread -1345328224 (LWP 8151)] [New Thread -1336935520 (LWP 7781)] [New Thread -1335608416 (LWP 7764)] [New Thread -1327215712 (LWP 7753)] [New Thread -1318823008 (LWP 7752)] [New Thread -1277846624 (LWP 7720)] [New Thread -1269417056 (LWP 7717)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 75801
Thread 1 (Thread -1232443728 (LWP 7708))
Hi, thanks for following up. Can you install the debug packages not just for evolution, but also for evolution-data-server, libbonobo, libglib2, gtk2, libgnomeui, ORBit2, and gtkhtml?
Created attachment 74514 [details] Text dump 1 from gdb (starting evolution from gdb)
Created attachment 74515 [details] Text dump 2 from gdb (starting gdb on bug buddy event)
I find out something watching the system monitor. 1. Evolution opens taking aprox 25 Mb. It can stay there for several minutes, as long as I don't get any email. 2. An email comes, the spamd and spamd-child processes rises from 2Mb to 25/30 Mb, then they go back to the 2 Mb boundary. 3. Inmediately after that, evolution starts growing its memory use: from 30 Mb 400 Mb in less than a minute in 30 Mb jumps every two seconds (I can watch the hard disk light at full speed). ¿Does it help?
*** Bug 361528 has been marked as a duplicate of this bug. ***
*** Bug 361432 has been marked as a duplicate of this bug. ***
*** Bug 361309 has been marked as a duplicate of this bug. ***
*** Bug 361296 has been marked as a duplicate of this bug. ***
*** Bug 361232 has been marked as a duplicate of this bug. ***
*** Bug 361205 has been marked as a duplicate of this bug. ***
(In reply to comment #2) > Every time Evolution crashes I send the bug buddy report. Now I have this > report numbers: 361205, 361232, 361296, 361309 & 361346 (one day use). Should I > stop sendig this reports? Yes, please. :) Don't report the very same crash again. > I am installing the evolution-dbg package now, in which report number should I > fill the results in case of a new crash? Please either add the stacktrace to this bug (you can get the stacktrace in the "details" of bug-buddy), or simply file /one/ new report and mention this bug number in the new one. Thanks! Regarding debugging packages: Please install them for evolution, evolution-data-server and gtkhtml, plus debugging packages for some basic GNOME libs. More details can be found here: http://live.gnome.org/GettingTraces/DistroSpecificInstructions
Also, when running Evolution inside gdb, wait till *after* the crash, when you get the gdb prompt again. Then run the command "thread apply att bt" at the gdb prompt. This will gather the necessary information of the application that just crashed before. :)
OK, Karsten. I will do that. By the way, Evolution does not crash every time I start it, but every single time it takes more than 300 Mb of the system memory. Sometimes even more than 500 Mb. I just can't use this program as it turns my computer into a dead turtle. Please help! Jorge
New dump, after the installation of dbg packages: Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.16.1 2006-10-02 (Ubuntu) BugBuddy Version: 2.16.0 Memory status: size: 768180224 vsize: 0 resident: 768180224 share: 0 rss: 452980736 rss_rlim: 0 CPU usage: start_time: 1160621761 rtime: 0 utime: 1042 stime: 0 cutime:842 cstime: 0 timeout: 200 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 -1233164624 (LWP 18696)] [New Thread -1337988192 (LWP 18714)] [New Thread -1329595488 (LWP 18713)] [New Thread -1278542944 (LWP 18712)] [New Thread -1286972512 (LWP 18705)] [New Thread -1270150240 (LWP 18702)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 75929
Thread 1 (Thread -1233164624 (LWP 18696))
I am considering not using Evolution anymore: it takes the ridiculous amount of 2.5 Gb Virtual Memory and 500 Mb of resident memory, by doing nothing, just being minimized on the applications bar... Then, when I want to close it, Evolution is so fat that it crashes. This is only happens before I get mail. If I managed to star Evolution "disconnected", then it keeps like a good beast: on the 25 mb boundary. But when I fetch some mail, it gets crazy: eating every single byte of available memory, in just few minutes. Everything else in my computer is working OK. I am starting the quest for a new PIM, unless there is something I can do to solve this. How can I help to fix this problem?
Thanks for taking the time to report this bug. However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use. By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME 2.22.3.