Bug 678291

Summary: [abrt] thunderbird-3.1.7-3.el6_0 killed by signal 11 [@ nsImapMailCopyState::~nsImapMailCopyState]
Product: Red Hat Enterprise Linux 6 Reporter: Siddharth <swaikar>
Component: thunderbirdAssignee: Jan Horak <jhorak>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1CC: cww, gecko-bugs-nobody, jwest, vgaikwad
Target Milestone: rcKeywords: Triaged
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-05 21:30:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
backtrace, disassembly none

Description Siddharth 2011-02-17 13:34:46 UTC 
Description of problem:

abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/thunderbird-3.1/thunderbird-bin
component: thunderbird
crash_function: raise
executable: /usr/lib64/thunderbird-3.1/thunderbird-bin
rating: 0
Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: 
How to reproduce: Don't know. It crashed overnight.
time: 1294986829
uid: 105

Resolution	 


Version-Release number of selected component (if applicable):
thunderbird-3.1.7-3.el6_0
Red Hat Enterprise Linux Workstation release 6.0 (Santiago)

How reproducible:
random crash

Steps to Reproduce:
1.
2.
3.
  
Actual results:
thunderbird crash

Expected results:
thunderbird should not crash 

Additional info:
Comment 1 Siddharth 2011-02-17 13:40:02 UTC 
Created attachment 479326 [details]
backtrace, disassembly
Comment 4 Chris Williams 2011-02-24 18:32:14 UTC 
This bug was not resolved before development freeze.  We are now making preparations for the launch of 6.1 and are only accepting critical and high impact bugs.  We're reflagging this bug for 6.2 to continue the review and work needed to resolve this bug.
Comment 5 Matěj Cepl 2011-03-08 15:04:55 UTC 
Similar upstream crash can be found in https://crash-stats.mozilla.com/report/index/e0fd5b91-5588-40c3-8b0f-2fcf12110301
Comment 6 Matěj Cepl 2011-03-08 15:09:41 UTC 
Please, describe the steps that led to this issue and how to reproduce it. What settings, networks, or configurations are needed to reproduce the issue?
Comment 8 Jeremy West 2011-10-05 21:30:23 UTC 
Closing this bug, since the associated customer case has closed.  Please feel free to re-open this if new information becomes available.