Closed Bug 1265073 Opened 8 years ago Closed 8 years ago

crash in shutdownhang | WaitForSingleObjectEx | WaitForSingleObject | PR_WaitCondVar | nsThread::ProcessNextEvent | mozilla::net::nsHttpConnectionMgr::Shutdown

Categories

(Firefox :: Untriaged, defect)

x86
Windows 10
defect
Not set
critical

Tracking

()

RESOLVED DUPLICATE of bug 1158189

People

(Reporter: noall97, Unassigned)

Details

Crash Data

This bug was filed from the Socorro interface and is 
report bp-0230128f-0ae9-4ebe-8d78-afd8f2160415.
=============================================================
This was the first crash report I received after accidentally downloading some conspicuous software that my computer had blocked I tried to cancel the download and firefox crashed. now it still opens but in safety mode, after refreshing everything, redownloading everything, whenever I try to search anything, open a bookmark, or anything in that matter besides checking the troubleshoot page it will not load and eventually crash. I have scanned my computer with AVG free antivirus and nothing came up I really enjoy using Mozilla firefox and I would like to know what else can be done to fix the problem or atleased help fix it. Incase my email isn't there please if you have any idea's as to what the issue is its noall97@hotmail.com
Component: General → Untriaged
Hi noall,

Can you please try a new clean Firefox install and provide your results?

Also, is this still reproducible on your end ? If yes, can you please retest this using latest FF release and latest Nightly build (https://nightly.mozilla.org/) and report back the results ? When doing this, please use a new clean Firefox profile, maybe even safe mode, to eliminate custom settings as a possible cause (https://goo.gl/PNe90E).

Thanks,
Paul.
Flags: needinfo?(noall97)
We already have a bug report on this crash, but it's possible the developers working on that bug might find information from you helpful.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.