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 572548 - SVN HEAD evo deadlocks -- stack traces
SVN HEAD evo deadlocks -- stack traces
Status: RESOLVED DUPLICATE of bug 568332
Product: evolution
Classification: Applications
Component: Mailer
2.26.x (obsolete)
Other All
: Normal critical
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2009-02-20 12:48 UTC by Reid Thompson
Modified: 2013-09-13 00:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Reid Thompson 2009-02-20 12:48:52 UTC 
Steps to reproduce:
1. leave evo running overnight, come in to deadlock
2. Including stack traces for evo, eds, evo-exchange
3. This is from SVN head build from yesterday, but it has been happening for several days at least.


Stack trace:
Evolution:
(gdb) cont
Continuing.
[New Thread 0xbd79fb90 (LWP 4394)]
[Thread 0xbd79fb90 (LWP 4394) exited]
[New Thread 0xbd79fb90 (LWP 4402)]
[Thread 0xbd79fb90 (LWP 4402) exited]
[New Thread 0xbd79fb90 (LWP 4452)]
[Thread 0xbd79fb90 (LWP 4452) exited]
[New Thread 0xbd79fb90 (LWP 4455)]
^C
Program received signal SIGINT, Interrupt.
[Switching to Thread 0xb66976c0 (LWP 24298)]
0xffffe424 in ?? ()
(gdb) thread apply all bt full

+ Trace 212729

in ../sysdeps/unix/sysv/linux/poll.c
(gdb) 

Other information:
Comment 1 Reid Thompson 2009-02-27 12:34:18 UTC 
This deadlock is happening pretty consistently.

Evolution:
(gdb) thread apply all bt full

+ Trace 212956
Comment 2 Milan Crha 2009-03-02 14:10:29 UTC 
Hmm, those two are different. The first seem to me as evo and eds are doing nothing, but eex is poking to your GAL, but has a bad time with a "broken pipe" signal.

In the second, it seems that evo is trying to read a message from your eex server and others does nothing.

Do you have any issue with your server during night, or some scheduled restarts, anything?
Comment 3 Reid Thompson 2009-03-02 14:51:55 UTC 
(In reply to comment #2)
> Hmm, those two are different. The first seem to me as evo and eds are doing
> nothing, but eex is poking to your GAL, but has a bad time with a "broken pipe"
> signal.
> 
> In the second, it seems that evo is trying to read a message from your eex
> server and others does nothing.
> 
> Do you have any issue with your server during night, or some scheduled
> restarts, anything?
> 

no issues that I am aware of.  This box is on a UPS and has no scheduled reboots.  ( and the system still has all apps running as i left them when leaving the previous evening ).
Comment 4 Reid Thompson 2009-03-12 12:02:07 UTC 
Evo:
(gdb) thread apply all bt full

+ Trace 213410

Thread 1 (Thread 0xb61f1aa0 (LWP 636))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 write
    from /lib/libpthread.so.0
  • #5 camel_write
    at ../../../evolution-data-server/camel/camel-file-utils.c line 523
  • #6 camel_write_socket
    at ../../../evolution-data-server/camel/camel-file-utils.c line 670
  • #7 camel_stub_marshal_flush
    at ../../../evolution-exchange/camel/camel-stub-marshal.c line 469
  • #8 mail_stub_return_progress
    at ../../../evolution-exchange/mail/mail-stub.c line 710
  • #9 refresh_folder_internal
    at ../../../evolution-exchange/mail/mail-stub-exchange.c line 1377
  • #10 polled
    at ../../../../../evolution-data-server/servers/exchange/lib/e2k-context.c line 2395
  • #11 final_finished
    at ../../../libsoup/libsoup/soup-session-async.c line 331
  • #12 IA__g_cclosure_marshal_VOID__VOID
    at ./gmarshal.c line 77
  • #13 IA__g_closure_invoke
    at ../../../glib/gobject/gclosure.c line 767
  • #14 signal_emit_unlocked_R
    at ../../../glib/gobject/gsignal.c line 3314
  • #15 IA__g_signal_emit_valist
  • #16 IA__g_signal_emit
    at ../../../glib/gobject/gsignal.c line 3034
  • #17 soup_message_finished
    at ../../../libsoup/libsoup/soup-message.c line 899
  • #18 soup_message_io_finished
    at ../../../libsoup/libsoup/soup-message-io.c line 172
  • #19 IA__g_cclosure_marshal_VOID__VOID
    at ./gmarshal.c line 77
  • #20 IA__g_closure_invoke
    at ../../../glib/gobject/gclosure.c line 767
  • #21 signal_emit_unlocked_R
    at ../../../glib/gobject/gsignal.c line 3244
  • #22 IA__g_signal_emit_valist
  • #23 IA__g_signal_emit
    at ../../../glib/gobject/gsignal.c line 3034
  • #24 socket_read_watch
    at ../../../libsoup/libsoup/soup-socket.c line 1116
  • #25 g_io_unix_dispatch
    at ../../../glib/glib/giounix.c line 162
  • #26 IA__g_main_context_dispatch
    at ../../../glib/glib/gmain.c line 1814
  • #27 g_main_context_iterate
    at ../../../glib/glib/gmain.c line 2448
  • #28 IA__g_main_loop_run
    at ../../../glib/glib/gmain.c line 2656
  • #29 bonobo_main
    at bonobo-main.c line 311
  • #30 main
    at ../../../evolution-exchange/storage/main.c line 278
  • #0 ?? 
in ../sysdeps/unix/sysv/linux/poll.c
(gdb)
Comment 5 Milan Crha 2009-03-12 12:19:39 UTC 
Reid, could you try to apply Matt's patch from bug #568332, please?
Long story short: I caused thread leaking when I wrote sqlite vfs in camel, thus after some time (like overnight), one could got out of threads (and memory), which very likely happened to you here. Please try and let me know. Thanks a lot.
Comment 6 Reid Thompson 2009-03-12 12:48:14 UTC 
(In reply to comment #5)
> Reid, could you try to apply Matt's patch from bug #568332, please?
> Long story short: I caused thread leaking when I wrote sqlite vfs in camel,
> thus after some time (like overnight), one could got out of threads (and
> memory), which very likely happened to you here. Please try and let me know.
> Thanks a lot.
> 

patch applied, rebuilding now
Comment 7 Akhil Laddha 2009-05-22 07:18:07 UTC 
Reid , ping , any update about this bug ?
Comment 8 Reid Thompson 2009-05-22 12:28:51 UTC 
(In reply to comment #7)
> Reid , ping , any update about this bug ? 
> 

I believe the patch remedied the problem for me.  I have not experienced this issue since applying it.
Comment 9 Akhil Laddha 2009-05-28 04:43:17 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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