stalled computation
Anonymous
3 Jul 2007 4:49:03 UTC
Topic 13560
(moderation:
If your result is actually stalled, it would be a good idea to look into the last line(s) of the stderr.txt in the slot directory of that result, and e.g. post it here.
At the very beginning, "Reading SFTs and setting up stacks..." can take quite some time, depending on the speed of the machine. Another operation that can take prety lomg depending on the history of the run is resuming from a checkpoint. While these are in progress, no progress counters etc. are updated.
Another possibility is that the communication between App, BOINC Client and Manager is broken somewhere in between. In these cases it might be helpful to open the App's graphics, as the progress counter displayed there is independent of the communication with the Core Client.
BM
stalled computation
)
Yes, it is. Unfortunately it only reveals that indeed it got stuck starting the Windows Runtime debugger. Someone should point Rom Walton (BOINC) to this.
(actually there is more it tells us: whatever the reason was for the general access violation, it didn't persist a restart of the App, as the result completed successfully afterwards)
Would be interesting to know is this is the only reason for stalled results, or if there are others.
Yep, that's what I meant.
BM
BM