Closed
Bug 438698
Opened 17 years ago
Closed 16 years ago
Firefox 3 crashes when downloading file if prism extension enabled
Categories
(Firefox :: Extension Compatibility, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 458158
People
(Reporter: maddentim, Unassigned)
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008060309 Firefox/3.0 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008060309 Firefox/3.0 See details in Ubuntu launchpad bug report: 236613 https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/236613 Basically, if you have the prism extension to create new webapps from current webpage enabled and download a file from the web, Firefox crashes. When started from terminal it just says "segmentation fault" following the crash. There are more details in the ubuntu report. Ubuntu came back and made the bug invalid, i guess because it's an extension, but I wanted to make sure someone fixed it as I like the thing. Reproducible: Always Steps to Reproduce: 1. install prism 0.2 extension (https://addons.mozilla.org/en-US/firefox/addon/6665) 2. download any old file 3. Firefox crashes Actual Results: Crash Expected Results: Download file and keep going The application Prism (0.8) is installed from the repositories on the system as well. It is only the extension that causes the crash. It might have something to do that the ubuntu repo is only on prism 0.8 when the latest is 0.9
Comment 1•17 years ago
|
||
Reproduced consistently on Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9) Gecko/2008061015 Firefox/3.0 ... with or without Prism installed from the repos.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•17 years ago
|
Severity: normal → major
Hardware: PC → All
Comment 2•16 years ago
|
||
I've been having the same problems, when I disabled prism the problems were gone.
Comment 3•16 years ago
|
||
Sorry, forgot build id: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1b1pre) Gecko/20081005 Minefield/3.1b1pre ID:20081005033754
Comment 4•16 years ago
|
||
Keep spamming, sorry for that, bugzilla should add an edit button... Anywaay, back to the topic. I think these are the bugreports that are related: http://crash-stats.mozilla.com/report/list?product=Firefox&branch=1.9.1&version=Firefox%3A3.1b1pre&query_search=signature&query_type=contains&query=&date=&range_value=1&range_unit=weeks&do_query=1&signature=nsJAR%3A%3AOpen(nsIFile*)
Comment 5•16 years ago
|
||
Hello, I have the same proble with firefox 3.1b3-pre (20090223 build) on Debian Lenny : Firefox segfaults when I download a file.
Comment 6•16 years ago
|
||
This problem occurs with Firefox 3.1b3 on Vista, including with a clean profile (save for the Refractor for Prism extension being installed), so its not just limited to Linux installs.
3.6 beta crashes on any download for me - hsa for several weeks now. Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2a1pre) Gecko/20090601 Firefox/3.0 ID:20090601052941 Clean profile no add-ons. Linux - I get a segv.
1 more piece of info - the download always completes - then the popup notifier comes on to advise that download has completed - the crash occurs when that notifier popup goes away - either waiting - or clicking the X on top right.
Comment 10•16 years ago
|
||
Crash Reporter cannot send through a proxy - so hand uploading the 2 crash files
Comment 11•16 years ago
|
||
Comment 12•16 years ago
|
||
https://bugs.launchpad.net/ubuntu/+source/firefox-3.0/+bug/236613/comments/6 is a duplicate of bug 458158
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Comment 13•16 years ago
|
||
Errr my crashes are still occurring on a clean profile with no extensions at all - as in comment #1 - prism is not required. The dup bug this was assigned to says it is fixed (closed) as of april build of trunk - it is definitely NOT fixed as of the june trunk builds. Unless fixed means fixed in private dev build but not released into any nightly/hourly build since april ?? The bug is definitely still in the current trunk builds.
You need to log in
before you can comment on or make changes to this bug.
Description
•