Bug 3097 - crashes when accessing different gmail folders or when deleting messages
Summary: crashes when accessing different gmail folders or when deleting messages
Status: RESOLVED WORKSFORME
Alias: None
Product: Claws Mail (GTK 2)
Classification: Unclassified
Component: Folders/IMAP (show other bugs)
Version: 3.9.3
Hardware: PC Linux
: P3 normal
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2014-02-27 18:57 UTC by rikrev2012
Modified: 2016-07-04 17:24 UTC (History)
0 users

See Also:


Attachments

Description rikrev2012 2014-02-27 18:57:45 UTC
i am using claws-mail 3.9.3 from Debian testing.

my usual crashes happen when trying to move among gmail folders and especially when deleting several messages one by one.

(gdb) thread apply all bt

Thread 59 (Thread 0x7fff55205700 (LWP 11777)):
#0  0x00007ffff1b7095d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ffff35d5194 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff35d529c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ffff35d52e9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007ffff35f91d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff4372e0e in start_thread (arg=0x7fff55205700) at pthread_create.c:311
#6  0x00007ffff1b7c0fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 12 (Thread 0x7fff797fa700 (LWP 6469)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fffe448dda3 in JSC::GCThread::waitForNextPhase() ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#2  0x00007fffe448de30 in JSC::GCThread::gcThreadMain() ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#3  0x00007fffe46beca1 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#4  0x00007ffff4372e0e in start_thread (arg=0x7fff797fa700) at pthread_create.c:311
---Type <return> to continue, or q <return> to quit---
Comment 1 rikrev2012 2014-03-01 13:30:20 UTC
another crash!

Thread 16 (Thread 0x7fff75605700 (LWP 6275)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fffe448dda3 in JSC::GCThread::waitForNextPhase() ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#2  0x00007fffe448de30 in JSC::GCThread::gcThreadMain() ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#3  0x00007fffe46beca1 in ?? ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#4  0x00007ffff4372e0e in start_thread (arg=0x7fff75605700) at pthread_create.c:311
#5  0x00007ffff1b7c0fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 15 (Thread 0x7fff75e06700 (LWP 6274)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fffe448dda3 in JSC::GCThread::waitForNextPhase() ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#2  0x00007fffe448de30 in JSC::GCThread::gcThreadMain() ()
   from /usr/lib/x86_64-linux-gnu/libjavascriptcoregtk-1.0.so.0
#3  0x00007fffe46beca1 in ?? ()
---Type <return> to continue, or q <return> to quit---
Comment 2 Paul 2014-03-01 13:33:51 UTC
Are you suggesting by your backtrace snippets that include libjavascriptcoregtk-1.0.so.0 that this is somehow related to the Fancy plugin??
Comment 3 rikrev2012 2014-03-01 14:06:14 UTC
hello Paul,

well although the backtrace mentions libjavascriptcoregtk it never crashed when i was reading or doing something that involved the fancy plugin, at least that i could see, maybe it was doing something in the background?

this last crash happened once again when i was deleting several emails from one gmail inbox.

the message that claws displayed was something like "BUILDING THREADS".

right now i have about 7 email accounts configured.

thanks
Comment 4 rikrev2012 2014-03-01 16:21:29 UTC
and another....

Thread 7 (Thread 0x7fffcf3a0700 (LWP 6686)):
#0  pthread_cond_wait@@GLIBC_2.3.2 ()
    at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007ffff2d636eb in mailsem_internal_wait () from /usr/lib/libetpan.so.15
#2  0x00000000005dd500 in thread_run (data=0xf472e0) at etpan-thread-manager.c:331
#3  0x00007ffff4372e0e in start_thread (arg=0x7fffcf3a0700) at pthread_create.c:311
#4  0x00007ffff1b7c0fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 3 (Thread 0x7fffd76a4700 (LWP 6672)):
#0  0x00007ffff1b7095d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ffff35d5194 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ffff35d529c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fffe756ea1d in ?? ()
   from /usr/lib/x86_64-linux-gnu/gio/modules/libdconfsettings.so
#4  0x00007ffff35f91d5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007ffff4372e0e in start_thread (arg=0x7fffd76a4700) at pthread_create.c:311
#6  0x00007ffff1b7c0fd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7fffe7567700 (LWP 6671)):
---Type <return> to continue, or q <return> to quit---
Comment 5 Michael Schwendt 2014-03-01 19:20:21 UTC
> Debian testing.

The backtraces are lacking all the interesting details, because you've not installed the -debug packages.

But see bug 3089 comment 2.


> my usual crashes happen when trying to move among gmail folders and
> especially when deleting several messages one by one.

With "usual crashes" you probably mean "most of the time it works, but sometimes Claws Mail crashes spontaneously". In case you're facing connection problems while accessing gmail via imap, the crash is likely just a side-effect.
Comment 6 rikrev2012 2014-03-01 19:37:13 UTC
prior to the 1st crash report i installed claws-mail-dbg after following claws wiki http://www.claws-mail.org/faq/index.php/Debugging_Claws

 apt-cache policy claws-mail claws-mail-dbg 
claws-mail:
  Installed: 3.9.3-1
  Candidate: 3.9.3-1
  Version table:
 *** 3.9.3-1 0
        500 http://debian.solydxk.com/production/ testing/main amd64 Packages
        100 /var/lib/dpkg/status
claws-mail-dbg:
  Installed: 3.9.3-1
  Candidate: 3.9.3-1
  Version table:
 *** 3.9.3-1 0
        500 http://debian.solydxk.com/production/ testing/main amd64 Packages
        100 /var/lib/dpkg/status

i don't have any connection problems, right now i am using a fiber line that has been running without any problems.

i have claws configured to fecth email every 10min, and i never seen it crash when updating my accounts.
Comment 7 Michael Schwendt 2014-03-01 20:55:12 UTC
> i installed claws-mail-dbg

You would need to install the debug package for *every* library that Claws Mail uses. As you can see in the stacktrace, the truncated parts you show are outside Claws Mail code.


> i don't have any connection problems, right now i am using a fiber line that
> has been running without any problems.

The IMAP connection to a Google Mail server can be interrupted/lost, too, for various reasons.
Comment 8 rikrev2012 2014-03-02 14:27:42 UTC
>You would need to install the debug package for *every* library that Claws Mail >uses. As you can see in the stacktrace, the truncated parts you show are outside >Claws Mail code.

how can i know what libs is claws using?

ldd *something* ?


>The IMAP connection to a Google Mail server can be interrupted/lost, too, for >various reasons.

i understand that, but i guess the problem is not there, weeks ago when gmail went down claws never crashed.
Comment 9 Michael Schwendt 2014-03-02 17:48:17 UTC
> how can i know what libs is claws using?
> ldd *something* ?

For example. But since you want to figure out which Debian packages the libraries are included in, you would need to query you package database for the package names. At Fedora one would simply run "debuginfo-install claws-mail", and that would install all -debuginfo packages with the help of a package dependency resolver.


> > The IMAP connection to a Google Mail server can be interrupted/lost,
> > too, for >various reasons.
> 
> i understand that, but i guess the problem is not there, weeks ago when
> gmail went down claws never crashed.

Well, then it would be even more important to generated full/detailed backtraces and also find out the steps how to reproduce the crash.

I am not a Claws Mail developer, just somebody who observed incoming problem reports at Fedora, and IMAP access together with GMail is Claws Mail's weak(est) spot for a very long time. It's not the only problem, however. Sometimes users are impatient when waiting for an IMAP action (facing a server connection timeout, for instance) and repeat the same mouse-clicks, which "sometimes" also manages to crash Claws Mail because of a race condition somewhere. Interrupting an active IMAP session (by going offline or stopping the network in Network Manager) is one way to crash Claws Mail, not reliably, but as a demonstration that something in that area is unstable.

That's why I've pointed at bug 3089 comment 2 and the other tickets linked there.

If you think you're facing an entirely different problem, more details will be needed.

Note You need to log in before you can comment on or make changes to this bug.