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 619996 - Evolution shuts down unexpectedly
Evolution shuts down unexpectedly
Status: RESOLVED DUPLICATE of bug 618347
Product: evolution-data-server
Classification: Platform
Component: general
2.28.x (obsolete)
Other Linux
: High critical
: ---
Assigned To: Evolution Shell Maintainers Team
Evolution QA team
evolution[passwords]
Depends on:
Blocks:
 
 
Reported: 2010-05-29 04:43 UTC by Takis Diakoumis
Modified: 2010-06-05 23:50 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
gdb trace log (115.47 KB, text/plain)
2010-05-29 04:43 UTC, Takis Diakoumis 		Details
evolution gdb trace - 2 (103.43 KB, text/x-log)
2010-05-30 07:10 UTC, Takis Diakoumis 		Details

Description Takis Diakoumis 2010-05-29 04:43:25 UTC 
Created attachment 162255 [details]
gdb trace log

evolution just shuts down at random times. i am not necessarily using it when this happens - i just notice it when i go back to it and its not there :)

running from a terminal and waiting, it predictably shuts down at some later point in time. terminal output is below:

takisd@fitter:~> evolution
** (evolution:6019): DEBUG: mailto URL command: evolution %s
** (evolution:6019): DEBUG: mailto URL program: evolution

** (evolution:6019): CRITICAL **: file gkr-operation.c: line 350
(gkr_operation_request): should not be reached

** (evolution:6019): CRITICAL **: file gkr-operation.c: line 350
(gkr_operation_request): should not be reached

***MEMORY-ERROR***: evolution[6019]: GSlice: assertion failed:
sinfo->n_allocated > 0
Aborted

it is usable, i just have to restart it again (...and again). it stays up for anything from minutes to hours. i also believe that any subsequent dumps and restarts cause it to shut down quicker the next time.

i ran a gdb trace - file is attached.
this bug was orginally posted here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=582895

let me know if i can provide any other info or assist in any other way.
Comment 1 Matthew Barnes 2010-05-29 13:46:00 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 and reopen this bug or report a new one. Thanks in advance!
Comment 2 Takis Diakoumis 2010-05-30 07:10:59 UTC 
Created attachment 162295 [details]
evolution gdb trace - 2
Comment 3 Takis Diakoumis 2010-05-30 07:14:45 UTC 
i ran again with additional dbg packages. 

the trace (at least to me) looks more complete after following directions from here http://live.gnome.org/GettingTraces/Details.

see attached - evolution-trace-2.log.

thanks
Takis
Comment 4 Matthew Barnes 2010-05-30 13:11:10 UTC 
Thanks, that does look better.  Appears to be crashing on a password prompt.
Comment 5 Akhil Laddha 2010-05-31 04:15:28 UTC 
looks dupe of bug 618347
Comment 6 Matthew Barnes 2010-06-05 23:50:59 UTC 
Seems to be the case.  The only active thread is in gnome_keyring_find_items_sync(), all the rest are idle.

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