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 419460 - crash in Evolution: I was just sitting and r...
crash in Evolution: I was just sitting and r...
Status: RESOLVED DUPLICATE of bug 376826
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-03-17 18:51 UTC by Steven Coco
Modified: 2007-04-12 21:36 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Steven Coco 2007-03-17 18:51:03 UTC 
What were you doing when the application crashed?
I was just sitting and reading a message in Evolution. I notice that it has again indeed leaked away all available swap space!


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

Memory status: size: -1125474304 vsize: 0 resident: -1125474304 share: 0 rss: 646889472 rss_rlim: 0
CPU usage: start_time: 1174152842 rtime: 0 utime: 13877 stime: 0 cutime:11599 cstime: 0 timeout: 2278 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 -1232546128 (LWP 5107)]
[New Thread -1559127136 (LWP 5248)]
[New Thread -1365247072 (LWP 5173)]
[New Thread -1327940704 (LWP 5129)]
[New Thread -1303397472 (LWP 5126)]
[New Thread -1278219360 (LWP 5125)]
[New Thread -1269826656 (LWP 5124)]
[New Thread -1295004768 (LWP 5120)]
[New Thread -1286612064 (LWP 5117)]
[New Thread -1259635808 (LWP 5114)]
[New Thread -1251243104 (LWP 5113)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 119507

Thread 7 (Thread -1269826656 (LWP 5124))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libc.so.6
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #6 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #7 IA__g_logv
    at gmessages.c line 497
  • #8 IA__g_log
    at gmessages.c line 517
  • #9 IA__g_realloc
    at gmem.c line 172
  • #10 g_array_maybe_expand
    at garray.c line 339
  • #11 IA__g_array_append_vals
    at garray.c line 132
  • #12 IA__g_byte_array_append
    at garray.c line 653
  • #13 camel_mime_part_construct_content_from_parser
    at camel-mime-part-utils.c line 71
  • #14 construct_from_parser
    at camel-mime-part.c line 961
  • #15 camel_mime_part_construct_from_parser
    at camel-mime-part.c line 989
  • #16 construct_from_parser
    at camel-multipart.c line 566
  • #17 camel_multipart_construct_from_parser
    at camel-multipart.c line 598
  • #18 camel_mime_part_construct_content_from_parser
    at camel-mime-part-utils.c line 119
  • #19 construct_from_parser
    at camel-mime-part.c line 961
  • #20 construct_from_parser
    at camel-mime-message.c line 590
  • #21 camel_mime_part_construct_from_parser
    at camel-mime-part.c line 989
  • #22 construct_from_stream
    at camel-mime-part.c line 1005
  • #23 camel_data_wrapper_construct_from_stream
    at camel-data-wrapper.c line 272
  • #24 pop3_get_message
    at camel-pop3-folder.c line 574
  • #25 camel_pop3_delete_old
    at camel-pop3-folder.c line 370
  • #26 pop3_sync
    at camel-pop3-folder.c line 309
  • #27 camel_folder_sync
    at camel-folder.c line 273
  • #28 fetch_mail_fetch
    at mail-ops.c line 345
  • #29 mail_msg_received
    at mail-mt.c line 570
  • #30 thread_dispatch
    at e-msgport.c line 987
  • #31 start_thread
    from /lib/tls/i686/cmov/libpthread.so.0
  • #32 clone
    from /lib/tls/i686/cmov/libc.so.6 






Comment 1


André Klapper





          2007-04-12 21:36:23 UTC
        



Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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