I don't run Universe@Home, so I think we can rule out any direct connection with that specific project. But I think the underlying cause is likely to be similar. Both of us have commented on the correlation with very high CPU demand.
I suspect that when the CPU running the client being monitored is very busy, it fails to respond to a Manager RPC within the time expected. From that failure, it wanders down an inappropriate error pathway and displays an assertive, but totally inaccurate, error message. That's not good UI design.
--
You received this message because you are subscribed to the Google Groups "boinc_alpha" group.
To unsubscribe from this group and stop receiving emails from it, send an email to boinc_alpha...@ssl.berkeley.edu.
To view this discussion on the web visit https://groups.google.com/a/ssl.berkeley.edu/d/msgid/boinc_alpha/a7c488d2-c51d-b49e-8016-196b3bdf483a%40pm.me.