For those of you who may be curious to how this turned out...
Quote:
After 2 days of life-force-sapping debugging,
I think I fixed this problem (to appear in the next release, as usual).
The problem wasn't specific to CPU throttling,
it could happen whenever you send an app lots of suspend/resume messages.
There was a bug in the API that could cause the app to occasionally
get stuck in a suspended state.
I fixed that, but since there are many apps already deployed
I also had to make the core client recognize when an app is in this state,
and kill/restart it.
For those of you who may be
)
For those of you who may be curious to how this turned out...
Kathryn :o)
Einstein@Home Moderator