Bug 7080 - firefox-14.0.1 always segfaults on File->Quit with my "Default" profile (including with -safemode)
Summary: firefox-14.0.1 always segfaults on File->Quit with my "Default" profile (incl...
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: Mageia 3
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-16 16:26 CEST by Shlomi Fish
Modified: 2013-09-18 12:53 CEST (History)
1 user (show)

See Also:
Source RPM: firefox-14.0.1-5.mga3.src.rpm
CVE:
Status comment:

Attachments
The backtrace of firefox in gdb. (128.83 KB, text/plain)
2012-08-16 16:27 CEST, Shlomi Fish 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Shlomi Fish 2012-08-16 16:26:19 CEST 
The Mageia Cauldron-shipped firefox-14.0.1 always segfaults on File->Quit with my "Default" profile (including with -safemode). I'll attach a gdb backtrace soon. This is annoying because when I start firefox again it asks me whether I should restore the tabs or not ("This is embarassing"/etc.).
Comment 1 Shlomi Fish 2012-08-16 16:27:09 CEST 
Created attachment 2648 [details]
The backtrace of firefox in gdb.
Comment 2 Sander Lepik 2012-08-16 16:43:17 CEST 
Does it also happen with new profile? Or with tarball version of Firefox?

CC: (none) => sander.lepik

Manuel Hiebel 2012-08-19 10:52:03 CEST

Assignee: bugsquad => dmorganec
Target Milestone: --- => Mageia 3

D Morgan 2013-09-18 00:04:44 CEST

Assignee: dmorganec => bugsquad

Manuel Hiebel 2013-09-18 11:43:26 CEST

Version: Cauldron => 3

Comment 3 Shlomi Fish 2013-09-18 12:53:41 CEST 
(In reply to Sander Lepik from comment #2)
> Does it also happen with new profile? Or with tarball version of Firefox?

I don't think it does, but can no longer check because my I'm now past Mageia 3 and firefox-14.0.1. Perhaps this bug should be closed.

Regards,

-- Shlomi Fish

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