Closed Bug 355187 Opened 18 years ago Closed 18 years ago

hang after going into search at something.com

Categories

(Firefox :: General, defect)

1.5.0.x Branch
x86
Windows XP
defect
Not set
critical

Tracking

()

RESOLVED INVALID

People

(Reporter: sk8judge, Unassigned)

Details

(Keywords: hang)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.7) Gecko/20060909 Firefox/1.5.0.7 I really covered everything in summary Reproducible: Always Steps to Reproduce: 1.Get out and come back in. Started orginally with setting up a login site with my Gas Company 2. 3.
Can you reproduce the problem with a new profile? http://kb.mozillazine.org/Profile_Folder
please limit summaries to a phrase or sentence. please supply URLs when a website is involved. The browser locks up when going into a search. Taskmgr shows browser loaded but no CPU being used if I delete the task then it will work. Seems to have started after I deleted Mcafee software. I have deleted and reloaded Firefox no improvement. At this stage getting frustrated. I want to use it but can not go on having problems. Any suggestions. Norm
Severity: major → critical
Component: Download Manager → General
Keywords: hang
Summary: stage getting frustrated. I want to use it but can not go on having problems. Any suggestions. Norm The browser locks up when going into a search. Taskmgr shows browser loaded but no CPU being used if I delete the task then it will work. Seems to have sta… → hang after going into search at something.com
Version: unspecified → 1.5.0.x Branch
No response from Norm, reporter, and not enough specific information here to investigate. If you can supply steps of what you typed and where to reproduce please reopen the bug. Bug guidance - http://www.mozilla.org/quality/bug-writing-guidelines.html For general help - http://forums.mozillazine.org/
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.