- 編集済み
High CPU usage causing fans to run at full throttle
I'm seeing unexpectedly high CPU usage for the Spine process on Mac OS X 10.8.2 even when it's just sitting idle in the background. It appears to be utilizing an entire core at all times. In the activity monitor I can see the processes' CPU usage fluctuating heavily between 20-60%.
The reason this bothers me is that the high processor usage causes the fans to run at full throttle whenever I'm working in Spine, which I find very annoying.
Other much more heavy applications including After Effects, Photoshop and Maya use nowhere near as much processing power (when idle) and do not cause the fans to spin up.
Any chance this can be addressed in future updates? (Currently using 1.2.3 but the behavior was similar in previous versions.)
I'm seeing this too.
Spine takes 92% of the CPU on my system while sitting in setup mode not using the app, specifically when the app is in the background.
When I run the app in the foreground it doesn't do it.
It also doesn't appear to do it when the app window is visible.... oddly it seems to only occur when the window is hidden.
This includes minimizing it to the dock. That seems to be the easiest way to reproduce it:
Open Spine, minimize to the dock, open Activity Monitor and watch it chew on the CPU.
Indeed, the CPU usage gets even worse when Spine is not the active application or behind another window. I'm writing this message in Firefox with Spine running in the background and it's just gobbling up CPU cycles to the point that there's significant lag when typing.
The same on Ubuntu although I just ignore this because many Java apps behave that way on Ubuntu on some version of OpenJDK at least.
libera-me wroteIndeed, the CPU usage gets even worse when Spine is not the active application or behind another window. I'm writing this message in Firefox with Spine running in the background and it's just gobbling up CPU cycles to the point that there's significant lag when typing.
When you say running in the background, can you clarify?
For me, as long as the window is somehow visible on the screen (even when Spine isn't the active window) it's fine. (4%-10% usage).
It's when the window is not visible (i.e. hidden behind something else, or minimized, or on a different space) that it starts pegging the CPU. (>90% usage).
So really, only when the window is hidden from view.
terrymisu wroteWhen you say running in the background, can you clarify?
When the Spine window is completely covered by another window (in this case Firefox) the processor usage goes through the roof: Stays between 90-95% until I bring Spine into the foreground, at which point the usage drops down to 20-60%.
However, even when Spine is the active application and fully in focus, it still uses way more CPU than it should when idle. I'm not playing an animation, not tweaking any values and for some reason Spine still uses a large amount of CPU cycles (apparently) just for redrawing the window. As I said earlier, other software including Maya and Photoshop does not exhibit this behavior.
Basically, whenever I turn on Spine I can expect the fans to spin up like crazy to the point that I dislike opening the application at all...
I am experiencing the same thing as libera-me. I have spine in the background behind a window and one of my cores was fully maxed out. I wouldn't have noticed it at all but my system began reacting a bit slow so I decided to check activity monitor and Spine was having a party.
We'll look into it, just fyi I have the same behavior going on here.
Yep, this was a bug. Will be fixed in v1.2.4, available soon.
Who writes gdx-texturepacker? Because it probably has the same bug (at least in the version I have, I always forget to update it). 
1.2.4 is available.
libgdx texture packer doesn't have this problem. It causes your fans to spin because it is doing a lot of work. Bin packing is NP hard and texture packer does some brute force to get the best result.
Still, it spins the fans a lot when not used for me (but not 100%, "only" 10-20%). But I'm using version 3.2.0, so maybe it's another GDX Texture Packer.