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 361205 - crash in Evolution: Closing evoluton, becaus...
crash in Evolution: Closing evoluton, becaus...
Status: RESOLVED DUPLICATE of bug 361346
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-10-10 17:20 UTC by jorgevalenciag
Modified: 2006-10-11 21:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description jorgevalenciag 2006-10-10 17:20:27 UTC 
What were you doing when the application crashed?
Closing evoluton, because the system monitor showed evolution was taking around 288 Mb of my memory, and the computer was very slow.


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

Memory status: size: 788049920 vsize: 0 resident: 788049920 share: 0 rss: 295321600 rss_rlim: 0
CPU usage: start_time: 1160495700 rtime: 0 utime: 6187 stime: 0 cutime:5199 cstime: 0 timeout: 988 it_real_value: 0 frequency: 1248

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 -1233389904 (LWP 5498)]
[New Thread -1310725216 (LWP 5867)]
[New Thread -1302332512 (LWP 5559)]
[New Thread -1301009504 (LWP 5542)]
[New Thread -1292006496 (LWP 5540)]
[New Thread -1283613792 (LWP 5539)]
[New Thread -1265259616 (LWP 5538)]
[New Thread -1256866912 (LWP 5503)]
[New Thread -1248437344 (LWP 5500)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 75650







Comment 1


Karsten Bräckelmann





          2006-10-10 17:29:58 UTC
        



Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.

Can you reproduce this?







Comment 2


Karsten Bräckelmann





          2006-10-11 21:20:09 UTC
        




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