Windows 10 reached EOS (end of support) on October 14, 2025. If you are on Windows 10, see this article.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo
Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.
Argivearre

cpu itilization on Yahoo Groups

Firefox Probleemoplossing
rotax beäntwurde
rotax
rotax

I have been noticing high CPU utilization 120-160 %, and mem usage of 1.47 gb and more when load this specific page: http://finance.yahoo.com/mb/OPK/

I would imagine this happens on any of the yahoo finance message boards for any stock. I have reset firefox, installed the latest release version and now beta version. Running Mac OS X 10.9.4 with 32 gb ram

I have been noticing high CPU utilization 120-160 %, and mem usage of 1.47 gb and more when load this specific page: http://finance.yahoo.com/mb/OPK/ I would imagine this happens on any of the yahoo finance message boards for any stock. I have reset firefox, installed the latest release version and now beta version. Running Mac OS X 10.9.4 with 32 gb ram

Alle antwurden (4)

guigs
guigs

Hi Rotax, Please see Fix Firefox using too much memory or CPU resources and Fix Firefox using too much memory or CPU resources for more troubleshooting steps.

rotax
rotax Fraacheigener

Yea, I did all that first. Then I isolated the condition to when this page is loaded.

rotax
rotax Fraacheigener

Here are some screen shots of the Mem and CPU. I only changed one thing and that was loading this page on Yahoo. http://finance.yahoo.com/mb/OPK/ Please try it yourself. Something on this page causes it. Not saying its a bug in Firefox, but perhaps it may be or there may be something that can be done to prevent the app from eventually locking up.

Bewurke troch rotax op

rotax
rotax Fraacheigener

Here are the screen shots after the page loads... could not view these for some reason in the previous post