WHY does classic environment eat all my CPU?

[annk]

I use Wenlin version 2.0, which requires classic environment (I'm running Tiger). But my CPU is up at 100% all the time when the program is open, even when nothing else is open. Activity Moniter shows "True Blue" as being the culprit - I assume that's classic? And if so, why does it eat all CPU?

 

[Mitthrawnuruodo]

Classic, aka True Blue Environment, tends to get a hiccup every now and then and eat all available resources. Just restart it from the Classic preference, and it should be OK.

 

[annk]

Ok, thanks. I'll do so next time. But it's a bummer to have to keep saving and reopening Wenlin...guess I'll have to fork out the cash for version 3.0. , to avoid classic

 

[Anonymous Freak]

It's also because Classic is a full OS. An OS that did not 'play well with others'. It is taking as much as it can, but the main OS X kernel (Mach) will take back anything it needs to give to another program. Basically, Classic is considered 'low priority'. If nothing else wants processor time, Classic will take it; but it something else DOES want it, Mach will force Classic to give it up.

 

[annk]

So my CPU usage will always be high when running classic, because the CPU that isn't being used by other programs, will automatically be sucked up by classic? How can an OS run if it sucks up all CPU??

Sorry, this is probably a dumb question, just trying to get it straight.

 

[Mitthrawnuruodo]

No, if Classic is running without any applications, it should use little or no resources. But, if a classic app is running it might take a bit, and often more than a similar OS X application, and especially if that application really, really wants attention (like a save or open dialogue), then Classic quickly will require all the resources it can.