Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On 28 September 2017 at 10:02, Charlie Fenton wrote: > But you are correct that my proposed change may be useful only for the > default screensaver graphics app (boincscr), which should never have > multiple instances running simultaneously. > I think the default

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

The client needs to know that some program is still using the slot directory. stderrgfx.txt isn't a perfect solution to the problem but I don't think there is any other mechanism to do it. I don't think the client really knows about graphics apps other than being some extra files it needs to

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On Sep 27, 2017, at 9:02 PM, Rom Walton wrote: > More than one graphics application can be running at a time, hence why the > graphics application log file ended up in the slot directory. Just creating > a single user specific subdirectory isn't going to lead to a happy

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

Charlie, More than one graphics application can be running at a time, hence why the graphics application log file ended up in the slot directory. Just creating a single user specific subdirectory isn't going to lead to a happy place. It is supposed to be cleaned up when the slot directory is

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On the Mac, the project graphics apps can not write to the per-user BOINC directory (which on the Mac is "/Users/{username}/Library/Application Support/BOINC/") because they run as user and group boinc_project under our UNIX account-based sandboxing. So I plan to set up a PR to create new

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

Yes, I’ll probably disable that. > On Sep 27, 2017, at 2:51 PM, Charlie Fenton wrote: > > On Sep 27, 2017, at 12:49 PM, Juha Sointusalo > wrote: >> I did see that the graphics app opens stderrgfx.txt file in slot directory >> and keeps it

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On Sep 27, 2017, at 12:49 PM, Juha Sointusalo wrote: > I did see that the graphics app opens stderrgfx.txt file in slot directory > and keeps it open as long as the graphics are open. That is not terribly useful, since it will be gone after the slot directory is

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

I assume DA is really busy now but it sounds like there’s a fix for the issue which is promising. Thanks everyone who contributed to this very helpful thread, particularly Juha for even running some tests. I’ll try to add some logic to make the error less fatal for a short term fix. regards,

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

It should be pointed out that the fix for this problem (eaf200e54d4d0bb0ce2ea84ec4f21409d7a80eb6) was available and drawn to David's attention before v7.8.2 was even built, let alone made the recommended version. On Wednesday, 27 September 2017, 21:52, Juha Sointusalo

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On 27 September 2017 at 23:39, David E Kim wrote: > Thanks for running these tests! > > So is it a windows only issue? It appears so for R@h. > Yep. Who is responsible for the BOINC client releases? > David Anderson. -Juha

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On 27 September 2017 at 22:49, Juha Sointusalo wrote: > I installed 7.8.2 a few minutes ago to make sure I can see the bug with > that version. It will take about one hour to get results. > Yep, it's the bug in 7.8.2. A Rosetta task exits and client tries to clean

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On 27 September 2017 at 01:17, David E Kim wrote: > Would a reversion or fix to the BOINC client be the best option to save > wasted computing and bandwidth? If indeed there is a bug? > I added Rosetta to my Windows host earlier today and run it on self built

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

Would a reversion or fix to the BOINC client be the best option to save wasted computing and bandwidth? If indeed there is a bug? So this has been a general finding with other projects? Sorry for this long thread. Thanks for all your help Juha. David K > On Sep 26, 2017, at 3:04 PM, Juha

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On 27 September 2017 at 00:47, David E Kim wrote: > But the errors only recently started to occur consistent with our recent > app release. > Yep. And 7.8.2 was just released three weeks ago just to muddy things. So it is a boinc client issue and not a boinc api issue?

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

It’s just on windows clients too. > On Sep 26, 2017, at 2:47 PM, David E Kim wrote: > > 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

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

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,

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On 26 September 2017 at 23:59, David E Kim 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

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

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! David K > On Sep 26, 2017, at 1:15 PM, Juha Sointusalo > wrote: > > Windows only, BOINC version 7.8.2 only? And

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

Windows only, BOINC version 7.8.2 only? And it's boinc_graphics_make_shmem() that fails? If it's 7.8.2 it looks like yet another case of using dirty slot directories. The shared memory segment's name that is really used contains the number of the slot directory. If the segment already exists

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

MB > On Sep 26, 2017, at 12:34 PM, Juha Sointusalo > wrote: > > On 26 September 2017 at 20:55, David E Kim > wrote: > > failed to create shared mem segment: minirosetta Size: 25001672 > > Are you trying to

Re: [boinc_dev] Increase in errors on Windows clients related to shared memory

On 26 September 2017 at 20:55, David E Kim wrote: > failed to create shared mem segment: minirosetta Size: 25001672 > Are you trying to create 25 GB shared memory segment? -Juha ___ boinc_dev mailing list