Closed
Bug 649985
Opened 14 years ago
Closed 11 years ago
Unusual high cpu-load for firefox exe, seems to be a conflict with yahoo messenger.exe
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: c4scst, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0) Gecko/20100101 Firefox/4.0
Getting "high" cpu-load for firefox.exe if i view a page with animated gifs (smiley-icons). The problem only occurs if Yahoo-Messenger (10 final) is running. As soon as YM is closed cpu of firefox.exe drops, even if it still views the gif's.
Was tested in Safemode and with YM 11beta...always the same problem. Also the Yahoo-Plugin witch comes with the messenger was removed, result was the same.
Reproducible: Always
Steps to Reproduce:
1.start firefox
2.start Yahoo messenger
3. view a page with animated gifs
Actual Results:
CPU of firefox.exe climbs to about 20%
Expected Results:
not eating my CPU
Updated•14 years ago
|
Version: unspecified → 4.0 Branch
Did some more Testing. Have the same issue with Firefox 4.0.1.
The same Test on Windows XP did not lead to high CPU usage.
Works for me on Mozilla/5.0 (Windows NT 6.1; rv:6.0a1) Gecko/20110510 Firefox/6.0a1
Could you see if the issue occurs if using an empty testing profile? (Don't install any addons into it)
http://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile
I tested it...it also happens with a new profile.
thx for your advice
Comment 4•11 years ago
|
||
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: 11 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.
Description
•