GNOME Bugzilla – Bug 402207
e_account_set_from_xml() leads to crash in xml parsing
Last modified: 2009-12-11 06:26:32 UTC
from bug 366448 , comment #6 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 106362
Thread 1 (Thread -1232578896 (LWP 5088))
goddamn cracktastic trace, confirming.
This doesn't seem to have particularly much to do with addressbook. Shell, misc, or mailer would be more suitable..
Do you have any exchange account enabled? I see some similar crashers with exchange, for more info see bug #497295 comment #6. Is it your case too?
Steven Coco reported it originally, CCing him on this report, and kindly asking him to answer the question.
Hi folks. It's been a long time since I saw Evolution crash. At that time I can definitely say I did not have any Exchange account activity at all. I am now using the Kubuntu/KDE4.1 desktop (this one: 2.6.24-19-generic #1 SMP Wed Aug 20 22:56:21 UTC 2008 i686 GNU/Linux). I'm using KMail and haven't actually run Evolution in quite some time. I saw some bug fixes come down after this crash, and as I remember, Evolution started to calm down a lot. Unfortunately, I may not be much use to you now since I have a whole new system here. I can't remember much more detail about how it was behaving: it would just allocate RAM the whole time it was open: I tested it once by letting it sit and run without doing anything on the machine, and eventually all the swap would get used up and the machine would just slow to a crawl. I seem to remember thinking it would wind up being a rendering issue: it seemed nearly definite that Evolution was either parsing or rendering because I would change the message preview by either selecting a different message in the inbox or by switching folders, which causes a new message to be previewed, and then it would likely hang right there a lot. If it did not crash, I do remember noticing at these points of activity my disk activity would go crazy and tons of swap would get allocated. And I may have a vague memory that if I specifically selected a message for preview that would require a fancier preview -- perhaps a mailing list digest message, which has all those multiple entries for each message -- that Evolution was more likely to sit and begin swapping tons of RAM for a noticeable length of time. So that made me suspect more that it was some parsing or rendering. That's probably all the useful feedback I can add at this time. Good luck!
Can we move this bug to obsolete now?
Dunno. We have a backreference in bug 500557 comment #1.
Tobias, different bug?
Yes, obviously, but I can't remember or search which one it was :(
Please feel free to reopen the bug if the problem still occurs with a newer version of GNOME 2.28.0 or later, thanks.