Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 92195 bytes cmdline: claws-mail component: claws-mail Attached file: coredump, 178155520 bytes crash_function: _int_malloc executable: /usr/bin/claws-mail kernel: 2.6.35.12-90.fc14.x86_64 package: claws-mail-3.7.9-2.fc14 rating: 4 reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1304521925 uid: 10625 How to reproduce ----- 1. I had notebook docked and had NetworkManager configure wired ethernet and wifi connection 2. I undocked, so the default connection switched to the wifi 3. Then in a minute or so I changed to a different wifi network. It took about 15 seconds to go through and while NM was still searching, I noticed that claws-mail has crashed. The machine was running after a pretty recent reboot with no updates applied after the reboot, so it should have been pretty stable. I tried to reproduce the crash, but seems random.
Created attachment 496905 [details] File: backtrace
Just like the memory corruption in bug 696680, which you've filed earlier. Last time malloc crashed when called from within glib2's gslice code, this time it's glib2's g_strdup. Another reporter has filed bug 689644 where glib2's g_malloc was the entry point. In which ways do you use the Python plugin? Your plugins: /usr/lib64/claws-mail/plugins/fancy.so /usr/lib64/claws-mail/plugins/pgpcore.so /usr/lib64/claws-mail/plugins/pgpinline.so /usr/lib64/claws-mail/plugins/pgpmime.so /usr/lib64/claws-mail/plugins/python_plugin.so /usr/lib64/claws-mail/plugins/smime.so Other reporter's plugins: /usr/lib64/claws-mail/plugins/address_keeper.so /usr/lib64/claws-mail/plugins/archive.so /usr/lib64/claws-mail/plugins/attachwarner.so /usr/lib64/claws-mail/plugins/geolocation_plugin.so /usr/lib64/claws-mail/plugins/gtkhtml2_viewer.so /usr/lib64/claws-mail/plugins/mailmbox.so /usr/lib64/claws-mail/plugins/notification_plugin.so /usr/lib64/claws-mail/plugins/perl_plugin.so /usr/lib64/claws-mail/plugins/pgpcore.so /usr/lib64/claws-mail/plugins/pgpmime.so /usr/lib64/claws-mail/plugins/python_plugin.so
Python plugin - in no way to be honest. I installed it to play with a bit, but haven't made the time :) So it's at the distribution default.
Package: claws-mail-3.7.9-5.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Put the disk subsystem under a fair amount of load (I was rsyncing large amounts of data + a bunch of random IO from MySQL and other small applications running in the background) 2. Select an email with attachments (my account was on IMAP, if that matters) 3. Try to click reply, forward or basically any operation witht the e-mail as quick as you can. Boom! Comment ----- It seems this is another race condition in claws-mail. While the disk subsystem is under significant load, I can trigger this 100%. If I select an e-mail, wait for a couple of seconds for claws to fully load it, everything works fine. The e-mail I triggered this on was in no way huge. About 43 KB in total. 2 ODT documents and a couple of lines of text.
Hmm, so it crashes sometimes even if the e-mail is loaded for a while.
Package: claws-mail-3.7.9-5.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Claws crashed in the background (I didn't touch it for minutes) right at the time where I lost my (weak) wifi connection and NetworkManager started spinning searching for a new one. 2. 3.
Package: claws-mail-3.7.9-5.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I clicked reply on a message in IMAP folder as a million times in the past 2. Boom we go! Claws freezes for a second thre with the reply button pressed and then crashes 3. I can reproduce this 100% 3a. I think this is reproducible only if I fast switch to the account and click reply before claws gets a chance to load (meta)data (?) as if I have the account open for a longer period the crash doesn't happen.
Ha, so I've already filed this. Weird it happens only once per month.
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping