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 410745 - crash in Evolution: I was closing a preview ...
crash in Evolution: I was closing a preview ...
Status: RESOLVED DUPLICATE of bug 340165
Product: evolution
Classification: Applications
Component: general
2.8.x (obsolete)
Other All
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2007-02-22 10:22 UTC by juanje.ojeda
Modified: 2007-04-09 15:10 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description juanje.ojeda 2007-02-22 10:22:48 UTC
What were you doing when the application crashed?
I was closing a preview of a attatched image to an email.


Distribution: Guadalinex v4 (toro)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 123084800 vsize: 0 resident: 123084800 share: 0 rss: 54157312 rss_rlim: 0
CPU usage: start_time: 1172139605 rtime: 0 utime: 529 stime: 0 cutime:495 cstime: 0 timeout: 34 it_real_value: 0 frequency: 0

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 -1208994128 (LWP 9741)]
[New Thread -1256203360 (LWP 9760)]
[New Thread -1247810656 (LWP 9759)]
[New Thread -1236276320 (LWP 9758)]
[New Thread -1227883616 (LWP 9748)]
[New Thread -1217442912 (LWP 9745)]
(no debugging symbols found)
0x429ac822 in ?? () from /lib/ld-linux.so.2

Comment 1 Susana 2007-02-22 12:29:34 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 juanje.ojeda 2007-02-23 13:08:27 UTC
Thanks to you for be interesting on.

I've installed the evolution-gdb package (for Ubuntu) and I'm waiting for the next crash ;-)

Anything special that should I do when it happens?

BTW, evolution crashes to me sometimes with large attachments like this time, but also freeze my sistem and finally crash with messages about the evolution got out of memory or something like that.

Sorry but I can't find the excatly message right now. I put it this because seems to me there is some kind of connection between both issues.

Greetings :-)
Comment 3 Susana 2007-02-27 12:25:05 UTC
Hi,

Besides evolution-dbg could you please also install:

evolution-data-server-dbg, libgtkhtml3.8-dbg, libglib2.0-0-dbg, libgtk2.0-0-dbg and libpango1.0-0-dbg

Then you need to reproduce the crash. Once bug-buddy pops up, you can find the stacktrace in the "details", now containing way more information. Please copy that stacktrace and paste it as a comment here.  Thanks!
Comment 4 juanje.ojeda 2007-03-27 18:34:40 UTC
Hi,

I did as you said and this is the output:

Distribution: Guadalinex v4 (toro)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 121204736 vsize: 0 resident: 121204736 share: 0 rss: 60608512 rss_rlim: 0
CPU usage: start_time: 1175020010 rtime: 0 utime: 1212 stime: 0 cutime:1110 cstime: 0 timeout: 102 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 -1212512592 (LWP 20935)]
[New Thread -1260184672 (LWP 20957)]
[New Thread -1251390560 (LWP 20956)]
[New Thread -1239422048 (LWP 20955)]
[New Thread -1231029344 (LWP 20951)]
[New Thread -1221026912 (LWP 20948)]
0x429ac822 in ?? () from /lib/ld-linux.so.2

Thread 1 (Thread -1212512592 (LWP 20935))

  • #0 ??
    from /lib/ld-linux.so.2
  • #1 waitpid
    from /lib/tls/i686/cmov/libc.so.6
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 segv_redirect
    at main.c line 426
  • #4 killpg
    from /lib/tls/i686/cmov/libc.so.6
  • #5 IA__g_hash_table_lookup
    at ghash.c line 231
  • #6 em_cache_lookup
    at e-msgport.c line 347
  • #7 em_icon_stream_is_resized
    at em-icon-stream.c line 326
  • #8 efhd_change_cursor
    at em-format-html-display.c line 1643
  • #9 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 84
  • #10 IA__g_closure_invoke
    at gclosure.c line 490
  • #11 signal_emit_unlocked_R
    at gsignal.c line 2440
  • #12 IA__g_signal_emit_valist
    at gsignal.c line 2209
  • #13 IA__g_signal_emit
    at gsignal.c line 2243
  • #14 gtk_widget_event_internal
    at gtkwidget.c line 3911
  • #15 IA__gtk_main_do_event
    at gtkmain.c line 1453
  • #16 gdk_event_dispatch
    at gdkevents-x11.c line 2320
  • #17 IA__g_main_context_dispatch
    at gmain.c line 2045
  • #18 g_main_context_iterate
    at gmain.c line 2677
  • #19 IA__g_main_loop_run
    at gmain.c line 2881
  • #20 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #21 main
    at main.c line 615
  • #0 ??
    from /lib/ld-linux.so.2

Comment 5 palfrey 2007-04-09 15:10:27 UTC
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


*** This bug has been marked as a duplicate of 340165 ***