Closed Bug 667393 Opened 13 years ago Closed 10 years ago

hangs all the time, hangs for a long time

Categories

(Firefox :: General, defect)

x86_64
Windows 7
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: anonymousperson, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:7.0a1) Gecko/20110626 Firefox/7.0a1
Build ID: 20110626030229

Steps to reproduce:

I actually don't have to do anything.  It constantly hangs.  I might be away from my computer and I come back and it's hanging.  It's starting to happen very frequently now.  I just cleared my history to see if that helps.  

I'm on windows 64 bit.  I have scanned and rescanned, I do not have a virus, everything works fine in chrome and I do not get this problem.  I have add ons/ extensions - shockwave (latest version), adblock 1.3.8 and adblock element hiding helper 1.1.1


Actual results:

The browser gets a blue circle and just circles for several minutes at a time.


Expected results:

I should be able to just surf the internet in FF but it's getting to be impossible to do this on FF browser.
I could not reproduce the issue on:
Mozilla/5.0 (Windows NT 6.1; rv:7.0a1) Gecko/20110626 Firefox/7.0a1

> The browser gets a blue circle and just circles for several minutes at a
> time.

Is it a specific website loaded when you get the hang? Could you attach a screenshot of that moment with the blue circle visible?
While hanged could you try to get a crash (i.e. a forced close)?
OS: Other → Windows 7
Hardware: All → x86_64
Reporter, do you still see this problem when using a current version in safe mode?   http://support.mozilla.org/kb/troubleshoot-firefox-issues-using-safe-mode

If you no longer see the problem, please set status to resolved and resolution to WORKSFORME.

If you do see the problem, please update comments on how to reproduce.
Whiteboard: [closeme 2014-02-01]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2014-02-01]
You need to log in before you can comment on or make changes to this bug.