Closed Bug 508488 Opened 16 years ago Closed 14 years ago

Mozilla stops responding when I access this site from address bar

Categories

(Firefox :: General, defect)

3.5 Branch
x86
Windows Vista
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: dvd_id10t, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2011-2-25])

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729) Mozilla hangs every time I try to access the URL above. It seems to stop responding to anything. Reproducible: Always Steps to Reproduce: 1. Enter URL into the address bar (copy/paste) 2. Hit enter 3. Watch Mozilla crash. The user who started this thread has the same problem, though s/he doesn't mention much. https://support.mozilla.com/tiki-view_forum_thread.php?comments_parentId=410146&forumId=1
Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3pre) Gecko/20090804 Shiretoko/3.5.3pre The site uses Java. Are you using the latest Java version?
Version: unspecified → 3.5 Branch
Reporter, Please update Firefox to 3.5.3 and Java to 6 update 15 or later.
Severity: critical → major
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing. http://support.mozilla.com/kb/Safe+Mode http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
No reply from reporter, INCOMPLETE. Please retest with Firefox 4 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
Fixed, works for me now with current release version of firefox.
Resolution: INCOMPLETE → FIXED
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.