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 364445 - crash in Evolution: closing the application ...
crash in Evolution: closing the application ...
Status: RESOLVED DUPLICATE of bug 334966
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-23 14:39 UTC by dinxter
Modified: 2006-10-28 00:00 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description dinxter 2006-10-23 14:39:10 UTC 
What were you doing when the application crashed?
closing the application by pressing the top right window close icon


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

Memory status: size: 306163712 vsize: 306163712 resident: 32161792 share: 19197952 rss: 32161792 rss_rlim: -1
CPU usage: start_time: 1161614226 rtime: 412 utime: 368 stime: 44 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47260714483008 (LWP 18649)]
[New Thread 1115703632 (LWP 18667)]
[New Thread 1107310928 (LWP 18666)]
[New Thread 1098918224 (LWP 18661)]
[New Thread 1090525520 (LWP 18658)]
[New Thread 1082132816 (LWP 18657)]
(no debugging symbols found)
0x00002afbb9cd55cf in waitpid () from /lib/libc.so.6

+ Trace 77860

Thread 6 (Thread 1082132816 (LWP 18657))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 5 (Thread 1090525520 (LWP 18658))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 4 (Thread 1098918224 (LWP 18661))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 3 (Thread 1107310928 (LWP 18666))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ??

Thread 2 (Thread 1115703632 (LWP 18667))

  • #0 select
    from /lib/libc.so.6
  • #1 e_msgport_wait
    from /usr/lib64/libedataserver-1.2.so.7
  • #2 e_msgport_reply
    from /usr/lib64/libedataserver-1.2.so.7
  • #3 start_thread
    from /lib/libpthread.so.0
  • #4 clone
    from /lib/libc.so.6
  • #5 ?? 






Comment 1


Karsten Bräckelmann





          2006-10-23 14:54:17 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!







Comment 2


dinxter





          2006-10-23 15:09:27 UTC
        



have installed debugging symbols but now cant seem to replicate the crash. have seen this crash recently once or twice before but it seems to involve a more complicated set of circumstances than just losing. will post more detail if i can replicate it.






Comment 3


dinxter





          2006-10-24 21:49:17 UTC
        



eventually managed to replicate the crash after a few dozen attempts on different days, i have no idea why it only crashes intermittently, i seemed to be doing exactly the same things. here's the stack trace with all the available debugging symbols (apart from libglib which i missed first time round) hope it helps. 

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

Memory status: size: 307806208 vsize: 307806208 resident: 32432128 share: 19537920 rss: 32432128 rss_rlim: -1
CPU usage: start_time: 1161726054 rtime: 439 utime: 408 stime: 31 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

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

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47431414992192 (LWP 14038)]
[New Thread 1115703632 (LWP 14056)]
[New Thread 1107310928 (LWP 14054)]
[New Thread 1098918224 (LWP 14053)]
[New Thread 1090525520 (LWP 14043)]
[New Thread 1082132816 (LWP 14042)]
0x00002b23785865cf in waitpid () from /lib/libc.so.6




+
Trace
    78124






Thread 1
          (Thread 47431414992192 (LWP 14038))


    

  • 
#0
waitpid

    
                from
                /lib/libc.so.6

    

    • 

  • 
#1
gnome_gtk_module_info_get

    
                from
                /usr/lib64/libgnomeui-2.so.0

    

    • 

  • 
#2
<signal handler called>

    • 

  • 
#3
strcmp

    
                from
                /lib/libc.so.6

    

    • 

  • 
#4
e_shell_window_set_title

    
                at e-shell-window.c
                  line
                  1247

    

    • 

  • 
#5
impl_ShellView_setTitle

    
                at e-shell-view.c
                  line
                  48

    

    • 

  • 
#6
GNOME_Evolution_ShellView_setTitle

    
                at Evolution-stubs.c
                  line
                  27

    

    • 

  • 
#7
e_component_view_set_title

    
                at e-component-view.c
                  line
                  136

    

    • 

  • 
#8
view_changed_timeout

    
                at mail-component.c
                  line
                  582

    

    • 

  • 
#9
g_source_get_current_time

    
                from
                /usr/lib64/libglib-2.0.so.0

    

    • 

  • 
#10
g_main_context_dispatch

    
                from
                /usr/lib64/libglib-2.0.so.0

    

    • 

  • 
#11
g_main_context_check

    
                from
                /usr/lib64/libglib-2.0.so.0

    

    • 

  • 
#12
g_main_loop_run

    
                from
                /usr/lib64/libglib-2.0.so.0

    

    • 

  • 
#13
bonobo_main

    
                from
                /usr/lib64/libbonobo-2.so.0

    

    • 

  • 
#14
??

    • 

  • 
#0
waitpid

    
                from
                /lib/libc.so.6

    

    • 













Comment 4


André Klapper





          2006-10-28 00:00:20 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 334966 ***