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 230764 - Crash: Segfault when exiting
Crash: Segfault when exiting
Status: RESOLVED DUPLICATE of bug 230632
Product: evolution
Classification: Applications
Component: Shell
unspecified
Other All
: Normal normal
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-09-20 10:37 UTC by Robert Claeson
Modified: 2002-09-20 16:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Robert Claeson 2002-09-20 10:37:13 UTC 
Package: Evolution
Priority: Normal
Version: GNOME2.0.2 1.1.1
Synopsis: Segfault when exiting
Bugzilla-Product: Evolution
Bugzilla-Component: Shell
Description:
Description of Problem:

After a 3 hour mail session, I exited Evolution by clicking the close
button on the window frame (Metacity wm). Evolution crashed with a
segfault.

Evolution is configured with 8 IMAP accounts with many subfolders.

Steps to reproduce the problem:
1. Start Evolution
2. Use it for a few hours
3. Exit

Actual Results:

Crash dialog box identifying the problem as a segfault.

Expected Results:

Evolution should exit without errors.

How often does this happen?

Intermittently. Not frequent enough to be readily reproducible. Note:
this problem also existed in Evolution 1.0.8.

Additional Information:

Using the Swedish locale in Red Hat Linux 7.2. Problem has also happened
when using the English locale.


Debugging Information:

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

[New Thread 1024 (LWP 2940)]
[New Thread 2049 (LWP 2986)]
[New Thread 1026 (LWP 2987)]
[New Thread 2051 (LWP 2988)]
[New Thread 3076 (LWP 2991)]
[New Thread 14341 (LWP 3024)]
[New Thread 15366 (LWP 3025)]
[New Thread 16391 (LWP 3032)]
[New Thread 17416 (LWP 3033)]
[New Thread 18441 (LWP 3034)]
[New Thread 19466 (LWP 3035)]
0x410f8369 in __wait4 () at __wait4:-1
	in __wait4

+ Trace 27563

Thread 3 (Thread 1026 (LWP 2987))

  • #0 __sigsuspend
    at ../sysdeps/unix/sysv/linux/sigsuspend.c line 45
  • #1 __pthread_wait_for_restart_signal
    at pthread.c line 969
  • #2 __pthread_alt_lock
    at restart.h line 34
  • #3 __pthread_mutex_lock
    at mutex.c line 120
  • #4 segv_redirect
    at main.c line 80
  • #5 pthread_sighandler
    at signals.c line 97
  • #6 <signal handler called>
  • #7 __pthread_mutex_lock
    at mutex.c line 99
  • #8 mail_async_event_emit
    at mail-mt.c line 647
  • #9 folder_changed
    at folder-browser.c line 834
  • #10 camel_object_trigger_event
    at camel-object.c line 882 


Unknown reporter: robert.claeson@terrabee.se, changed to bugbuddy-import@ximian.com.
Setting qa contact to the default for this product.
   This bug either had no qa contact or an invalid one.
Comment 1 Gerardo Marin 2002-09-20 16:56:10 UTC 

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