Bug 410345 – Evolution: Memory status: size: 153...

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 410345 - Evolution: Memory status: size: 153...


Summary:	Evolution: Memory status: size: 153...


Status:	RESOLVED DUPLICATE of bug 339602

Product:	evolution
Classification:	Applications
Component:	general
Version:	2.8.x (obsolete)
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Evolution Shell Maintainers Team
QA Contact:	Evolution QA team

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-02-21 11:29 UTC by ismaelarias
Modified:	2007-06-12 16:02 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description ismaelarias 2007-02-21 11:29:04 UTC

What were you doing when the application crashed?
Memory status: size: 153677824 vsize: 0 resident: 153677824 share: 0 rss: 32673792 rss_rlim: 0
CPU usage: start_time: 1172057200 rtime: 0 utime: 1513 stime: 0 cutime:1203 cstime: 0 timeout: 310 it_real_value: 0 frequency: 455

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

(no debugging symbols found)
Using host libthread_db library "/lib/i686/libthread_db.so.1".
(no debugging symbols found)
`shared object read from target memory' has disappeared; keeping its symbols.
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1236031264 (LWP 11911)]
[New Thread -1339032672 (LWP 11930)]
[New Thread -1337525344 (LWP 11928)]
[New Thread -1293300832 (LWP 11927)]
[New Thread -1310086240 (LWP 11923)]
[New Thread -1301693536 (LWP 11922)]
[New Thread -1284908128 (LWP 11916)]
[New Thread -1276515424 (LWP 11915)]
[New Thread -1268122720 (LWP 11914)]
[New Thread -1259730016 (LWP 11913)]
0xbfffe410 in __kernel_vsyscall ()

+ Trace 112553

Thread 5 (Thread -1310086240 (LWP 11923))

#0 __kernel_vsyscall
#1 __lll_mutex_lock_wait
from /lib/i686/libpthread.so.0
#2 _L_mutex_lock_71
from /lib/i686/libpthread.so.0
#3 pthread_kill
from /lib/i686/libpthread.so.0
#4 <signal handler called>
#5 camel_index_add_name
from /usr/lib/libcamel-1.2.so.0
#6 camel_folder_summary_info_new_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#7 camel_folder_summary_add_from_parser
from /usr/lib/libcamel-provider-1.2.so.8
#8 camel_mbox_summary_new
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#9 camel_mbox_summary_new
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#10 camel_local_summary_check
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#11 camel_local_folder_construct
from /usr/lib/evolution-data-server-1.2/camel-providers/libcamellocal.so
#12 camel_folder_refresh_info
from /usr/lib/libcamel-provider-1.2.so.8
#13 mail_empty_trash
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#14 mail_enable_stop
from /usr/lib/evolution/2.8/components/libevolution-mail.so
#15 e_msgport_wait
from /usr/lib/libedataserver-1.2.so.7
#16 start_thread
from /lib/i686/libpthread.so.0
#17 clone
from /lib/i686/libc.so.6




Distribution: Mandriva Linux release 2007.0 (Official) for i586
Gnome Release: 2.16.0 2006-09-04 (Mandriva)
BugBuddy Version: 2.16.0

Comment 1 ismaelarias 2007-02-21 12:18:34 UTC

necesito leer mis mails

I need read my mails

Comment 2 palfrey 2007-02-21 13:50:12 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 3 palfrey 2007-06-12 16:02:41 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 339602 ***