Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'A small collection of performance hints' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
A small collection of performance hints
Authored by: Bioinformatics on Apr 07, '03 05:48:35PM

You can get this effect if Classic crashes out on you - or at least I do...

What happens with me is like this: I open an ancient copy of Word under Classic (can't justify the ridiculous price of the OS X version). I work for a bit then eventually hide Word and go off working on other stuff with OS X apps, leaving Word and Classic lurking in the background. Eventually, hidden in the background, Word does a nasty (what's new?) and ties up Classic. (Its a pain: here is an app which is being left to itself, yet it manages to crash out... and it happens with disgusting regularity)

If you look at 'top' in Terminal at this point, you'll see TruBluEnv (Classic) taking up basically all the CPU that is available after other apps have been given their chance to execute. So if the other apps are taking a little shy of 20% (incl. top itself), TruBluEnv wil show a little over 80%. Basically Classic has gone ape-shit.

Use option-command-escape to bring up Force Quit and kill off Word and Classic. Look at top again and things ought to be more sane...

[ Reply to This | # ]