Closed Bug 790153 Opened 12 years ago Closed 12 years ago

Firefox Crashes since 15.0.1 update

Categories

(Firefox :: Untriaged, defect)

15 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 774281

People

(Reporter: codehyena, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

I updated from version 14 to version 15 and then 15.0.1


Actual results:

Firefox since updating to version 15.0.1 continually says that my zip file downloads are invalid and denied (when if you open the downloads manager and double click the file it opens them correctly)

Firefox locks up and crashes multiple times in one browing session, even on pages such as google's homepage.


Expected results:

Zip files should be able to be downloaded without issues or error messages.

Firefox shouldn't be crashing in the way it should, which leads to a suspicion of possible vulnerability.
Do you have links to crash reports from about:crashes ?
I have this link (see below) from 11th September 2012 from the about:crashes location.

https://crash-stats.mozilla.com/report/index/0709c791-4540-468b-8d2a-256ce2120912
That's a flash crash and there have been recent updates there as well. The timing could be coincidence because there was only one small change in 15.0.1 and nothing to do with plugins. Although maybe it happened in 15 too and you just didn't run that one long enough to experience the crash.

This is a pretty generic flash crash that has been around for a while.
Group: core-security
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Are you using Trusteer Rapport?
I did have trusteer Rapport installed a while back but its been gone for ages.

As for running a version long enough to experience a crash, I've been running each version since they were released. I downloaded 15 when it was released and 15.0.1 downloaded automatically not too soon afterwards.
You need to log in before you can comment on or make changes to this bug.