Closed Bug 151424 Opened 23 years ago Closed 23 years ago

Browser takes 100% utilization

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: shifleyb, Assigned: Matti)

References

()

Details

(Keywords: hang)

From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461; .NET CLR 1.0.3705) BuildID: 2002053012 Shortly after installing a new skin on the browser ( sorry, I do not remember the name of the skin, however it is a BLUE skin ) I was playing around cutting and pasting Url's into the browser, then the system seemed to freeze. Further inspection showed me that the CPU was running in the high 90%+ range. I killed the browser through task manager, and then started it again. The brower immediately went to 90%+ again, on your home page. I fully uninstalled Mozilla 1.0. Re-installed. The browser still had the blue skin on it, and was still killing my CPU. I uninstalled again, this time I even went and removed all registry entries the Mozilla 1.0 had ever been on the system. I also ensured that the install directory was gone. Re-installed, again blue skin and a CPU that is at 90%+ HELP Reproducible: Always Steps to Reproduce: 1. See above 2. 3. Actual Results: Its still broken Expected Results: Tht an uninstall would fix it
Please delete all files in Profile/Chrome (you will loose all additional language packs and third-party Themes) See the release notes for the profile location (it's in the OS user directory)
Reporter, did following the directions in comment 1 of this bug resolve the problem? Please resolve bug as worksforme if so or leave comment with information if not.
Your recommendation fixed the problem. Sorry for not getting back to you sooner. Closing bug
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
This is resolved incorrectly.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
-> WFM. Someone please mark this verified.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
I have confirmed that your recommended fix worked on my system
Status: VERIFIED → CLOSED
argh, please don't use "close"
Status: CLOSED → UNCONFIRMED
Resolution: WORKSFORME → ---
.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago23 years ago
Resolution: --- → WORKSFORME
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.