Just running my app and sitting there with a couple of windows open, and one single thread running (but basically idle, in a Sleep(50) loop) I’m seeing CPU usage hovering around 81%. This is on Mac OS X 10.8.4, and shows up both in a Built app and when running from the IDE.
Exact Same app, running in 2013 R2 : cpu hovers around 2%.
Well, the thread sleeps 99% of the time. But the main thread is the problem.
In 2013r2 it sleeps also 98% of the time.
But in 2013r3 the traces show that some heavy work is done with a timer and a lot of CF objects. Maybe Xojo engineers added a timer there to do some background work?
I was reporting this same problem on Windows during beta cycle (Beta 5, the first beta I was checking).
So I’m not alone: MAC too has this fault and maybe it is not related to single/multicore cpu.
Has anyone found a workaround/solution to this? There was a bug in R1 thread.suspend that I worked around by using thread.sleep. But now in R3 that’s using 100% CPU, too (as noted above). The only “solution” I’ve found is to go back to Xojo R1 (R2 isn’t usable for me for other reasons).
Thanks, although from a post by Joe on this thread it seems that the Cocoa and the Windows thread CPU-use bugs may not be related. I hope the fix applies to both, of course.