GNOME Bugzilla – Bug 519536
crash in activity_info_free at e-activity-handler.c:157
Last modified: 2013-09-13 00:59:18 UTC
Version: 2.22.x What were you doing when the application crashed? Clicked on the "Failure" icon on the statusbar. Distribution: Gentoo Base System release 2.0.0_rc6-r1 Gnome Release: 2.21.92 2008-02-27 (Gentoo) BugBuddy Version: 2.20.1 System: Linux 2.6.25-rc3-00081-g7704a8b #11 SMP PREEMPT Thu Feb 28 09:43:44 EET 2008 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10400090 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: gnome Memory status: size: 558579712 vsize: 558579712 resident: 53788672 share: 21704704 rss: 53788672 rss_rlim: 18446744073709551615 CPU usage: start_time: 1204295786 rtime: 3747 utime: 3461 stime: 286 cutime:26 cstime: 45 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' Using host libthread_db library "/lib/libthread_db.so.1". [Thread debugging using libthread_db enabled] [New Thread 0x7f115095f6f0 (LWP 16092)] [New Thread 0x4275f950 (LWP 16110)] 0x00007f114d0b2fbf in __libc_waitpid (pid=17538, stat_loc=0x7fff5899f130, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 in ../sysdeps/unix/sysv/linux/waitpid.c
+ Trace 190856
Thread 1 (Thread 0x7f115095f6f0 (LWP 16092))
0x00007f114d0b2fbf 41 in ../sysdeps/unix/sysv/linux/waitpid.c The program is running. Quit anyway (and detach it)? (y or n) [answered Y; input not from terminal] ----------- .xsession-errors (13637 sec old) --------------------- Error (51287): Illegal character '>' Error (51297): Missing 'endstream' Error (48160): Illegal character '>' Error (48170): Missing 'endstream' Error (66665): Illegal character '>' Error (66675): Missing 'endstream' Error (65782): Illegal character '>' Error (65792): Missing 'endstream' Error (48160): Illegal character '>' Error (48170): Missing 'endstream' Error (48160): Illegal character '>' Error (48170): Missing 'endstream' Error (57053): Illegal character '>' Error (57063): ...Too much output, ignoring rest... --------------------------------------------------
Thanks for that stacktrace :) Is this issue perfectly reproduceable?
Not perfectly, but it happens quite reliably under laggy network connection (like satellite internet).
Bumping version to a stable release.
*** Bug 533877 has been marked as a duplicate of this bug. ***
*** Bug 531695 has been marked as a duplicate of this bug. ***
*** Bug 536861 has been marked as a duplicate of this bug. ***
*** Bug 525349 has been marked as a duplicate of this bug. ***
*** Bug 537232 has been marked as a duplicate of this bug. ***
*** Bug 537343 has been marked as a duplicate of this bug. ***
Ok, I am now getting this quite reliably when pressing the error messages icon (stop sign). The stack trace remains the same:
+ Trace 200785
Created attachment 113012 [details] [review] fix-error-crasher.patch Ok, I managed to track down the cause, but I cannot figure out what is going on there, so someone who wrote this code first place should take a look :)
I think I got the issue.
Created attachment 113048 [details] [review] Test patch Try this patch. It should solve it. I wrote about correctly freeing 'data' But forgot that info needs to be freed which lies inside data. This should fix it.
Unless my eyes are deceiving me, the latest "Test patch" does absolutely nothing. Pointer info = data->info; and then replaces all uses of data->info with info. Summary: no change what so ever?!
Andreas :) Nope, it does something. The info is valid, but the holder data, dies/freed with the last task widget. but the info is still valid. So I preserve the info and free it later. It must work, if my assumptions are right.
Committed to stable/trunk.
This got in as r35702 (just for later reference).
*** Bug 535363 has been marked as a duplicate of this bug. ***
*** Bug 576365 has been marked as a duplicate of this bug. ***
*** Bug 585113 has been marked as a duplicate of this bug. ***
bug 601978 looks dupe which has been filed against 2.28.x