Bug 17429 - TB is segfaulting after being up for a few minutes
Summary: TB is segfaulting after being up for a few minutes
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Florian Hubold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-31 20:08 CET by Frank Griffin
Modified: 2016-01-01 16:54 CET (History)
2 users (show)

See Also:
Source RPM: thunderbird-38.5.0-2.mga6
CVE:
Status comment:

Attachments
stdout/stderr running TB from command line (29.25 KB, text/plain)
2015-12-31 20:10 CET, Frank Griffin 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Frank Griffin 2015-12-31 20:08:57 CET 
As of this morning's cauldron update, Thunderbird starts but segfaults after being up for a few minutes.  This happens reliably.

When it does, it prints messages about how to attach gdb to debug it, and then waits for something like 5 minutes before giving up and terminating.

I'll attach the stdout/stderr.

Reproducible: 

Steps to Reproduce:
Comment 1 Frank Griffin 2015-12-31 20:10:56 CET 
Created attachment 7315 [details]
stdout/stderr running TB from command line
Comment 2 Marja Van Waes 2015-12-31 20:47:27 CET 
Thanks for the report.

I understood, from the "[dev] Re: [changelog] [RPM] cauldron core/release thunderbird-38.5.0-2.mga6" thread on dev ml, that Florian is working on it, so assigning to him

CC: (none) => marja11
Assignee: bugsquad => doktor5000
Source RPM: thunderbird => thunderbird-38.5.0-2.mga6

Comment 3 Florian Hubold 2016-01-01 09:13:11 CET 
Yep, patch has already been added, build should hit the mirrors soon as thunderbird-38.5.0-4.mga6

For more details see
https://ml.mageia.org/wwsympa-wrapper.fcgi/arc/dev/2015-12/msg00568.html
and
https://ml.mageia.org/wwsympa-wrapper.fcgi/arc/dev/2015-12/msg00587.html

Status: NEW => ASSIGNED
CC: (none) => doktor5000
Hardware: x86_64 => All

Comment 4 Frank Griffin 2016-01-01 16:54:31 CET 
Looks like it's fixed.  Thanks !

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.