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 373244 - crash in em_cache_lookup: View picture reading mail
crash in em_cache_lookup: View picture reading mail
Status: RESOLVED DUPLICATE of bug 351374
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: 2006-11-10 03:50 UTC by lorenco
Modified: 2007-04-12 20:16 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16

Attachments
Crash Report (226.93 KB, text/plain)
2007-01-31 04:27 UTC, lorenco 		Details

Description lorenco 2006-11-10 03:50:13 UTC 
What were you doing when the application crashed?
View picture reading mail (clicked the arrow to drop down)


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 260345856 vsize: 0 resident: 260345856 share: 0 rss: 39657472 rss_rlim: 0
CPU usage: start_time: 1163129504 rtime: 0 utime: 1659 stime: 0 cutime:1508 cstime: 0 timeout: 151 it_real_value: 0 frequency: 1

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 -1232701776 (LWP 9171)]
[New Thread -1425343584 (LWP 9375)]
[New Thread -1380709472 (LWP 9329)]
[New Thread -1334887520 (LWP 9328)]
[New Thread -1330119776 (LWP 9295)]
[New Thread -1320309856 (LWP 9257)]
[New Thread -1302561888 (LWP 9218)]
[New Thread -1294169184 (LWP 9217)]
[New Thread -1285776480 (LWP 9216)]
[New Thread -1277383776 (LWP 9215)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 84943







Comment 1


André Klapper





          2006-11-10 11:30:28 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful
in determining the cause of the crash. Could you please install some debugging
packages [1] and reproduce the crash, if possible?

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!


[1] debugging packages for evolution, evolution-data-server and gtkhtml,
    plus debugging packages for some basic GNOME libs. More details can
    be found here:
    http://live.gnome.org/GettingTraces/DistroSpecificInstructions







Comment 2


André Klapper





          2006-11-17 08:45:27 UTC
        



Unfortunately the stacktrace does not have any hints about the real cause of
the crash and does not help in debugging this issue.

For some yet unknown reason, such stacktraces are pretty common currently on
certain distros. However, almost all of them do turn out to be filed already,
once we managed to gather a useful stacktrace. To do so, simply install the
corresponding debugging packages and reproduce the issue, if possible. The
resulting stacktrace (see bug-buddy details) will help us to identify and fix
the issue.


Just in case you ever can reproduce this crash later, please consider
installing debugging packages [1] and either reopen this bug report or simply
file a new one with the resulting stacktrace.  Thanks!

Closing this bug report as no further information has been provided.


Also, please feel free to report any further bugs you find.  Thanks!






Comment 3


lorenco





          2007-01-31 04:27:24 UTC
        



Created attachment 81566 [details]
Crash Report






Comment 4


lorenco





          2007-01-31 04:28:24 UTC
        



I just happen to get this again!

Have all Debugs installed so here is the crash report....






Comment 5


André Klapper





          2007-02-01 10:31:56 UTC
        



good trace, thanks for coming up with that one. looks unique in the database.
posting it here so it can be recognized by the duplicate-finder scripts:





+
Trace
    107066






    

  • 
#4
<signal handler called>

    • 

  • 
#5
IA__g_str_hash

    
                at gstring.c
                  line
                  95

    

    • 

  • 
#6
IA__g_hash_table_lookup

    
                at ghash.c
                  line
                  231

    

    • 

  • 
#7
em_cache_lookup

    
                at e-msgport.c
                  line
                  347

    

    • 

  • 
#8
em_icon_stream_get_image

    
                at em-icon-stream.c
                  line
                  272

    

    • 

  • 
#9
efhd_image_resized

    
                at em-format-html-display.c
                  line
                  1633

    

    • 

  • 
#10
IA__g_cclosure_marshal_VOID__BOXED

    
                at gmarshal.c
                  line
                  566

    

    • 

  • 
#11
IA__g_closure_invoke

    
                at gclosure.c
                  line
                  490

    

    • 













Comment 6


André Klapper





          2007-04-12 20:16:18 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 351374 ***