Jord sent me the email below and I have opened issue #1909 for it. The original 
poster to the forum wrote that the problem occurs in BOINC Manager version 
7.6.20 and later, but not in 7.6.18. since I had saved the source trees for 
versions 7.6.18 and 7.6.21, I compared these and found the following 
differences which would affect the manager:

in clientgui/BOINCGUIApp.cpp, .h: 
   added call to wxhandleFatalExceptions() in CBOINCGUIApp::OnInit()
   added new OnFatalException() method

in lib/gui_rpc_client_ops.cpp, .h:
  added support for "platform" entry in RESULT::parse()
  added result->platform argument to lookup)app_version() call in 
CC_STATE::parse()
  added suport for "platform" entry in CC_STATE::lookup_app_version()

I suspect the changes in gui_rpc_client_ops.cpp may be the problem, since (I 
presume) the older remote clients he is trying to manage don't have this field 
and I don't see any provision in the newer RPC code to deal with this situation.

Cheers,
--Charlie

On May 8, 2017, at 3:45 PM, Jord van der Elst <[email protected]> wrote:

> Hi Charlie,
> 
> In https://boinc.berkeley.edu/dev/forum_thread.php?id=11607 a user finds that 
> his BOINC 7.6.33 freezes when he connects to a remote client. 
> 
> In his words:
> "While trying to view remote computer's tasks list (about to 300 tasks to 
> view), update speed is once in 5-10 seconds and whole client goes 
> unresponsive between updates. This makes client unusable. Tested with two 
> different client computers and multiple remote computers on same LAN."
> 
> He has tried varies versions and finds that they work until 7.6.1, then 
> someplace between that and 7.6.22 it breaks and is still broken. 
> 
> Any ideas? 
> 
> Thanks,
> 
> -- Jord van der Elst.
> 
> Hope you had a pleasant holiday, although it could've probably been a bit 
> warmer... :)

_______________________________________________
boinc_dev mailing list
[email protected]
https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.

Reply via email to