INTERACT FORUM
More => Old Versions => Media Center 12 (Development Ended) => Topic started by: Mr ChriZ on October 12, 2007, 05:20:22 am
-
I've seen this on my SMF Forum as well.
The news fader causes 100% CPU usage when your
on the front page everytime it fades.
This isn't a problem for meatier machines, but
it kills my Athlon Machine If I forget about it and
have it open in the background.
Could it be turned off?
-
I'm running an Intel core 2 6700 and firefox. When fading, firefox spikes at 3% cpu usage.
Surely there must be something else going on for you on your machine?
-
My system also shows a huge spike of 3% during fades. It lowlines at 2% when not fading. Good thing it doesn't fade continuously or my CPU may overheat. Core2 6300 I believe.
I bet you don't have the latest/correct video card drivers installed--then reboot twice before trying it.
-
I'm running an Intel core 2 6700 and firefox. When fading, firefox spikes at 3% cpu usage.
Surely there must be something else going on for you on your machine?
Through Firefox it's fine, but I tend to access Interact through MC's built in browser (ie IE),
since there's a link to it straight off the front page.
Do you find it only uses 3% with this?
-
See what happens if you use IE outside of MC.
-
Tried latest Nvidia drivers.
Graphics card is an MX 440 so not exactly beefy.
It happens when using IE7 directly as well
Anyone else got an older machine to try this?
I've got a Dell Vostro laptop here as well, and I can see
that it's not causing high cpu usage on this...
-
Sorry, I'm running the ATI HD 2900XT graphics card.
-
8800GTX graphics here.
Interesting... when viewed using IE7, cpu spikes up to 39% during fade, which would be what, 90%-ish on a single core CPU?
wonder why it does that....
-
I'm seeing this as well. "iexplore.exe" spikes to 99% as the current item fades out, and again as the new item fades in. This is on a P4 2.5 with a Geforce 6800GT using the latest drivers.
Larry
-
Anyone else got an older machine to try this?
It's probably not the age of the machine so much as it is the power of the video card that makes the difference. But the fade-in / fade-out shouldn't be that big a load on any card. Odd.
-
I blame Microsoft.
-
It's probably not the age of the machine so much as it is the power of the video card that makes the difference. But the fade-in / fade-out shouldn't be that big a load on any card. Odd.
I don't think it's a graphics card power issue. Even a low end graphics card -- or even software rendering for that matter -- can do a simple fade. This acts like something else. I think it's an Internet Explorer issue -- some sort of bug with the particular implementation of code on the page in combination with IE7. 99% CPU activity is WAY more than a fade should EVER take.
Larry
-
I don't think it's a graphics card power issue. Even a low end graphics card -- or even software rendering for that matter -- can do a simple fade. This acts like something else. I think it's an Internet Explorer issue -- some sort of bug with the particular implementation of code on the page in combination with IE7. 99% CPU activity is WAY more than a fade should EVER take.
Larry
Agreed
-
I blame Microsoft.
Which is why I blame Microsoft, maker of the dreaded IE. It's probably an extra, infinite loop to be stopped after rendering the fade that they didn't catch.
-
Which is why I blame Microsoft, maker of the dreaded IE. It's probably an extra, infinite loop to be stopped after rendering the fade that they didn't catch.
Regardless of whose fault it is, the real question becomes how can it be fixed. MS may have made some basic changes to IE7 that cause problems to occur in the code on that page -- something that wasn't a problem with IE6. This could classify as MS's "fault," but the fix could end up being something relatively easy for someone familiar with web page code.
Larry
-
I would say that it's the IE rendering engine. The code used to fade text--likely some javascript and css adjustments is almost definitely accurate in it's code syntax. It's just the browser's fault for not rendering the effect quickly and cleanly.