David Surovell wrote:
Folks,
I've noticed the CPU problem, but it went away for me after a check-in
late Tuesday afternoon. The problem has been caused before by the
UpdateUI stuff, also by my wxMSW composited window shim.
UpdateUI shouldn't cause infinite loops updating windows -- but I double
checked that it isn't causing the problem. Is there an easy way to turn
off wxMSW composited window shim to verify that it isn't part of the
infinite update problem?
My (strong) belief is that this problem is due to Chandler code
changes, and not wx. The wx code hasn't changed at all for a week, and
no significant low-level changes in wxMSW for some days before.
Regards,
David S.
=====================
Katie Capps Parlante wrote:
Is there any way to automate a test for this?
It would be great if we could be flagged when a new checkin
reintroduces this kind of problem.
Cheers,
Katie
John Anderson wrote:
Hi David:
Morgen noticed that Chandler pegs the CPU on windows. Other people have
noticed it's started getting sluggish a few days ago. It looks like
were
stuck in an infinite loop updating the screen. Seems to not happen on
win2k, which sounds like a bug you had awhile back with your offscreen
buffer fix. Any ideas?
John
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
