GNOME Bugzilla – Bug 573263
Crash in reset_layout (text) at e-text.c:429
Last modified: 2009-06-25 18:44:35 UTC
What were you doing when the application crashed? Open Evolution, Go to Calendar, It asked me password for Tripit (www.tripit.com) calendar (it wasn't necesasry because the password is saved, and it worked also if I clicked "ok" without insert anything) Evolution crashed Distribution: Fedora release 10 (Cambridge) Gnome Release: 2.24.3 2009-01-16 (Red Hat, Inc) BugBuddy Version: 2.24.2 System: Linux 2.6.27.15-170.2.24.fc10.x86_64 #1 SMP Wed Feb 11 23:14:31 EST 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10503000 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Nodoka Icon Theme: Fedora Memory status: size: 1089126400 vsize: 1089126400 resident: 105111552 share: 24776704 rss: 105111552 rss_rlim: 18446744073709551615 CPU usage: start_time: 1235649036 rtime: 5755 utime: 5165 stime: 590 cutime:23 cstime: 60 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/evolution' [Thread debugging using libthread_db enabled] [New Thread 0x7fc76c72f7e0 (LWP 856)] [New Thread 0x7fc75f72c950 (LWP 6308)] [New Thread 0x7fc74077c950 (LWP 6307)] [New Thread 0x7fc75eadb950 (LWP 886)] 0x0000003ec2e0ec2f in __libc_waitpid (pid=6348, stat_loc=0x7fff75843c50, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL);
+ Trace 212924
Thread 1 (Thread 0x7fc76c72f7e0 (LWP 856))
----------- .xsession-errors --------------------- warning: the debug information found in "/usr/lib/debug/lib64/libfreebl3.so.debug" does not match "/lib64/libfreebl3.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//usr/lib64/libnssckbi.so.debug" does not match "/usr/lib64/libnssckbi.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/usr/lib64/libnssckbi.so.debug" does not match "/usr/lib64/libnssckbi.so" (CRC mismatch). warning: the debug information found in "/usr/lib/debug//lib64/libattr.so.1.1.0.debug" does not match "/lib64/libattr.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/lib64/libattr.so.1.1.0.debug" does not match "/lib64/libattr.so.1" (CRC mismatch). --------------------------------------------------
can be related to bug #364236
*** Bug 578898 has been marked as a duplicate of this bug. ***
*** Bug 580882 has been marked as a duplicate of this bug. ***
*** Bug 581563 has been marked as a duplicate of this bug. ***
This is where the instance got freed. Note frame #39, it freed itself while using internal data.
+ Trace 215380
Thread 1 (Thread 0x7ffff3b9f7f0 (LWP 14301))
Created attachment 134502 [details] [review] proposed evo patch for evolution; As this is mostly out of hands of evolution, then caching values from gconf and not reading them each draw might help here on a performance side and also on the (not) crashing side. I cannot think of anything better.
What about this bug? Have this patch been accepted?
Patch status says None , it means patch is awaiting review comments and based on review comments, patch may be committed or may not.
*** Bug 584833 has been marked as a duplicate of this bug. ***
Milan, caching code seems fine to me. But howz this patch related to the bug? Im missing that.
(In reply to comment #10) > Milan, caching code seems fine to me. But howz this patch related to the bug? > Im missing that. > When you look to the stacktrace:
+ Trace 215930
then that the get_font_options calls gconf, which allows ORBit to proceed the Modified event from the calendar, which removed the EText itself. Caching the value and not calling the gconf in get_font_options will not call ORBit and everything will work as expected. A bit complicated, I agree, but works as expected, maybe is also a bit quicker.
Created commit ba01281 in evo master. (2.27.3+)
Created commit 88cf03f in evo gnome-2-26. (2.26.3+)
*** Bug 585585 has been marked as a duplicate of this bug. ***
*** Bug 586313 has been marked as a duplicate of this bug. ***
*** Bug 586970 has been marked as a duplicate of this bug. ***