But the errors only recently started to occur consistent with our recent app release.
So it is a boinc client issue and not a boinc api issue? The latest official client release for windows platforms is buggy? Another option (albeit not a good one) is to not use graphics. DK > On Sep 26, 2017, at 2:40 PM, Juha Sointusalo <juha.sointus...@gmail.com> > wrote: > > On 26 September 2017 at 23:59, David E Kim <de...@u.washington.edu > <mailto:de...@u.washington.edu>> wrote: > Ok, if that’s the case maybe it is related to using the same “prog_name”. > That definitely wouldn’t help the situation. > > I’ll test that change. Thanks! > > That could help at start while you still have tasks for both apps but > assuming you plan on moving all tasks to the new app I think you'll only get > a temporary reduction in error rate. If the problem is what I think it is the > only real solution is to get users to move to a working client version. > > -Juha _______________________________________________ boinc_dev mailing list boinc_dev@ssl.berkeley.edu https://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
