QT Player object is processor hog?

[Karl Becker]

I've noticed a disturbing problem with projects where I've used player 
objects.  Once I play them, even if I send a "stop player" command to 
stop it, the processor is just being chewed up by MetaCard.  However, 
once I delete the player object, or reload MetaCard without the player 
being used, the processor usage goes back down to being nice.

Why is the player object taking up so many proc cycles for me?

(On a similar note, it seems like MC gets slower as its being run for a 
log time on one system... like it gobbles up more resources the longer 
it runs.  But that's just a general thing I've noticed... a friend of 
mine testing out a project for me said there were 3 threads on his 
Windows box that were started by my program but, even after he quit it, 
were still there.  Odd.)

Thanks,
Karl