After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 364944 - crash in Evolution: Cairo crash This doesn't...
crash in Evolution: Cairo crash This doesn't...
Status: RESOLVED INCOMPLETE
Product: gtk-engines
Classification: Deprecated
Component: clearlooks
2.8.x
Other All
: High critical
: ---
Assigned To: Richard Stellingwerff
gtk-engines maintainers
: 382235 406715 453566 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-10-25 09:53 UTC by Thomas M.
Modified: 2007-09-09 15:41 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Thomas M. 2006-10-25 09:53:35 UTC 
What were you doing when the application crashed?
Cairo crash
This doesn't seem to be related to a specific evolution operation (I had just selected my INBOX after having selected the Trash mailbox).


Distribution: Debian 3.1 (sarge)
Gnome Release: 2.15.91 2006-08-13 (Debian)
BugBuddy Version: 2.16.0

Memory status: size: 182149120 vsize: 0 resident: 182149120 share: 0 rss: 69160960 rss_rlim: 0
CPU usage: start_time: 1161766247 rtime: 0 utime: 7760 stime: 0 cutime:7397 cstime: 0 timeout: 363 it_real_value: 0 frequency: 51

Backtrace was generated from '/usr/bin/evolution-2.8'

Using host libthread_db library "/lib/tls/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208649504 (LWP 25725)]
[New Thread -1301828688 (LWP 810)]
[New Thread -1260184656 (LWP 25793)]
[New Thread -1278612560 (LWP 25792)]
[New Thread -1269171280 (LWP 25791)]
[New Thread -1260782672 (LWP 25790)]
[New Thread -1251464272 (LWP 25735)]
[New Thread -1240929360 (LWP 25732)]
[New Thread -1232540752 (LWP 25730)]
[New Thread -1223758928 (LWP 25729)]
[New Thread -1215370320 (LWP 25727)]
0x4b0bf231 in __waitpid_nocancel () from /lib/tls/libpthread.so.0

+ Trace 78204

Thread 7 (Thread -1251464272 (LWP 25735))

  • #0 __lll_mutex_lock_wait
    from /lib/tls/libpthread.so.0
  • #1 _L_mutex_lock_29
    from /lib/tls/libpthread.so.0
  • #2 ??
  • #3 ??
  • #4 ??
  • #5 _dl_rtld_di_serinfo
    from /lib/ld-linux.so.2
  • #6 segv_redirect
    at main.c line 435
  • #7 segv_redirect
    at main.c line 435
  • #8 <signal handler called>
  • #9 memset
    from /lib/tls/libc.so.6
  • #10 e_memchunk_alloc0
    at e-memory.c line 178
  • #11 parse_term_new
    at e-sexp.c line 816
  • #12 parse_value
    at e-sexp.c line 1000
  • #13 parse_values
    at e-sexp.c line 868
  • #14 parse_value
    at e-sexp.c line 1009
  • #15 e_sexp_parse
    at e-sexp.c line 1287
  • #16 camel_folder_search_search
  • #17 imap_search_by_expression
  • #18 camel_folder_search_by_expression
  • #19 regen_list_regen
    at message-list.c line 3718
  • #20 mail_msg_received
    at mail-mt.c line 570
  • #21 thread_dispatch
    at e-msgport.c line 987
  • #22 start_thread
    from /lib/tls/libpthread.so.0
  • #23 clone
    from /lib/tls/libc.so.6 






Comment 1


André Klapper





          2006-12-05 23:25:27 UTC
        



this is either a cairo or a gtk-engines issue, also see the stacktrace of bug 382235.






Comment 2


André Klapper





          2006-12-05 23:25:37 UTC
        



*** Bug 382235 has been marked as a duplicate of this bug. ***






Comment 3


palfrey





          2007-01-07 17:07:33 UTC
        



*** Bug 384865 has been marked as a duplicate of this bug. ***






Comment 4


palfrey





          2007-01-07 17:07:39 UTC
        



*** Bug 368869 has been marked as a duplicate of this bug. ***






Comment 5


palfrey





          2007-01-07 17:07:48 UTC
        



*** Bug 384866 has been marked as a duplicate of this bug. ***






Comment 6


palfrey





          2007-01-07 17:08:03 UTC
        



*** Bug 388049 has been marked as a duplicate of this bug. ***






Comment 7


palfrey





          2007-02-21 14:01:39 UTC
        



*** Bug 406715 has been marked as a duplicate of this bug. ***






Comment 8


Benjamin Berg





          2007-04-03 16:40:04 UTC
        



Tom, should bug 384865, bug 368869, bug 384866 and bug 388049 maybe be duplicates of some other bug? I don't see anything in the stack traces that suggests a clearlooks issue.






Comment 9


palfrey





          2007-04-11 22:26:10 UTC
        



(In reply to comment #8)
> Tom, should bug 384865, bug 368869, bug 384866 and bug 388049 maybe be
> duplicates of some other bug? I don't see anything in the stack traces that
> suggests a clearlooks issue.

Yes. Not sure why I marked those as dupes... sifting through them now.






Comment 10


Benjamin Berg





          2007-04-26 18:14:37 UTC
        



Ah, of course. All of the bug reports have the following stack trace in common (except for the gnome-terminal one of course):





+
Trace
    130740






    

  • 
#8
<signal handler called>

    • 

  • 
#9
memset

    
                from
                /lib/tls/libc.so.6

    

    • 

  • 
#10
e_memchunk_alloc0

    
                at e-memory.c
                  line
                  178

    

    • 








Also most people seem to be reporting that this happens when working with the trash folder (kinda reminds me of bug 349816). So I am wondering whether there may be an evolution bug. However that does not explain the gnome-terminal problem.

That said, I don't know what may be causing this.






Comment 11


palfrey





          2007-07-04 12:57:29 UTC
        



*** Bug 453566 has been marked as a duplicate of this bug. ***






Comment 12


Benjamin Berg





          2007-09-09 15:41:06 UTC
        



Closing as incomplete. I have no idea where this bug could be coming from. It could be a bug in evolution or even cairo.

OH, and the lastest duplicate is definitely not a gtk-engines issue. It is either cairo or popplers fault there.

That said, if someone is able to reproduce this consistently or can get a valgrind log maybe that would be awesome. Feel free to reopen the bug if any more information gets available.