Does this still happen with Poser 3.4? People have often reported problems with Poser eating up CPU time on Windows. I never see it myself, so I don't know where that eating occurs. I've always suspected the serial emulation code, however. Poser creates separate threads for reading and writing serial data. Sometimes, those threads can get into a situation where they end up making Windows calls over and over because those Windows calls keep errorring out. Poser 3.4 now should correctly be clearing the error condition, allowing those threads to work (and sleep) properly.
-- Keith Rollin -- Palm OS Emulator engineer At 11:11 AM -0800 2/19/02, Evan Wise wrote: >I have also seen something of this in 2k where it will chew up 99% CPU while >in the background. > >To reproduce do the following: >-start and end a debug session (I use CW) >-press the Cancel button on the "Please wait" dialog CW pops up (it annoys >me) >-you can see POSEr reset in the background >-continue to code away in CW >--CPU is pinned (usually) >--I fix this by doing a soft reset of the emu manually > >If this helps the emu folks... > >E/. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
