-
Notifications
You must be signed in to change notification settings - Fork 514
Open
Milestone
Description
I've noticed several times recently that the MW@h multi-thread app
(MilkyWay@Home N-Body Simulation 1.72 (mt))
is running and accumulating CPU time very slowly (like 1% of real time) but not making progress.
It seems to be deadlocked in some way.
If I restart things, it goes back to normal (for a while).
We (or MW@h) needs to figure out why this is happening;
I suspect CPU throttling is involved; I haven't seen it when not throttling.
But it also raises the question of whether the client should do something in situations like this - maybe restart the app if it's not accumulating CPU time fast enough.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Type
Projects
Status
Backlog