Bug 749177 - [abrt] claws-mail-3.7.9-5.fc14: _int_malloc: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Summary: [abrt] claws-mail-3.7.9-5.fc14: _int_malloc: Process /usr/bin/claws-mail was ...
Keywords:
Status: CLOSED DUPLICATE of bug 759143
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d471852f7c870d766ff76732273...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-26 12:14 UTC by David Kovalsky
Modified: 2014-03-31 23:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 13:10:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (99.92 KB, text/plain)
2011-10-26 12:14 UTC, David Kovalsky
no flags Details

Description David Kovalsky 2011-10-26 12:14:19 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 102321 bytes
cmdline: claws-mail
comment: I've filed similar abrt reports related to changing network and claws crash. Likely related or even same issues of stale IMAP handle (or something like that).
component: claws-mail
Attached file: coredump, 103698432 bytes
crash_function: _int_malloc
executable: /usr/bin/claws-mail
kernel: 2.6.35.14-100.fc14.x86_64
package: claws-mail-3.7.9-5.fc14
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1319630597
uid: 10625

How to reproduce
-----
1. Pick up notebook from dock with both wired + wifi network
2. Move into a meeting room, reconnect lost wifi
3. Try to forward an e-mail

Comment 1 David Kovalsky 2011-10-26 12:14:23 UTC
Created attachment 530277 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-10-26 13:39:21 UTC
> Likely related or even same issues of stale IMAP handle
> (or something like that).

Not at all.

What may be similar is your usage pattern. The crash, however, is deep in memory allocation with a glib2 call finally failing in glibc due to whatever may have corrupted the memory before.

#15 0x0000003325213df1 in g_object_new at gobject.c:1296
...
#3  0x0000003366c7bace in __posix_memalign at malloc.c:6315
...
#0  0x0000003366c77b46 in _int_malloc at malloc.c:4538

Comment 3 abrt-bot 2012-03-30 13:10:12 UTC
Backtrace analysis found this bug to be similar to bug #759143, closing as duplicate.

Bugs which were found to be similar to this bug: 
  DeviceKit-disks: bug #579968
  claws-mail: bug #696680, bug #789636
  evince: bug #615380
  evolution: bug #744469
  evolution-data-server: bug #607960, bug #799718
  evolution-exchange: bug #669649
  gnome-shell: bug #759143, bug #781780
  gvfs: bug #571349
  pcmanfm: bug #789628
  rhythmbox: bug #681163, bug #709834, bug #748661
  xfce4-sensors-plugin: bug #772409

This comment is automatically generated.

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


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