App killed due to CPU usage? (EXC_RESOURCE WAKEUPS)

Question

Created Sep ’15

Replies 2

Boosts 0

Views 5.6k

Participants 2

On devlopment kit hardware, my app is occasionally getting terminated unexpectedly. In the crash log, I'm finding the message below. A quick search suggests that this is due to excessive thread waking and the CPU utilization / battery impact it's likely to have on mobile hardware. I'm having a little trouble making heads or tails of it, particularly since previous versions of the app never ran into trouble on hardware as old as the iPhone 4. Should it even be possible to trigger on tvOS, given that the device is guaranteed to be plugged-in? Any thoughts would be appreciated. Thanks!

Exception Type: EXC_RESOURCE

Exception Subtype: WAKEUPS

Exception Message: (Limit 150/sec) Observed 154/sec over 300 secs

Exception Note: NON-FATAL CONDITION (this is NOT a crash)

Triggered by Thread: 0

Boost

Answer 1

OP

Apple

Sep ’15

The key line from that log:

Exception Note: NON-FATAL CONDITION (this is NOT a crash)

Your app is not being killed

0

Answer 2

rdowling OP

Sep ’15

Thanks. That was my initial belief as well, but the timestamp sure did coincide perfectly with getting dumped back to the home screen and there were no other crash logs in the same time frame. I guess that means more testing... Maybe I still haven't gotten all the incantations correct to mitigate accidental bumps to a game controlelr's "B" button! 🙂

0