What does status "Waiting for shared memory" mean?

Keith

You can read more about the issue here:

http://boinc.berkeley.edu/dev/forum_thread.php?id=1871

Doing this will fix it:

http://www.spy-hill.net/help/apple/SharedMemory.html

Use the numbers they suggest unless you have an 8-way, then I suggest you double the max values.

---

Dublin, California
Team: SETI.USA

This is not quite the same problem as that you have mentioned in the links.
I am only running SETI on BOINC with this computer (and not multiple projects).
As is shown in the details below, it would seem that there were 2 successful tasks reported at 07:52:55 and 08:42:56 in each case followed by 2 tasks aborted by project as "no longer required", but misleadingly shown as "Reporting 2 tasks" (and even more misleadingly shown aborted as "Client Error" on the computer "Results" page).
Here is a copy of the Messages page after I had suspended 8 tasks in SETI in order to replicate the position I had obtained on a previous occasion:

Mon 9 Jul 07:52:45 2007|SETI@home|Computation for task 27fe00ab.6539.32633.286082.3.228_1 finished
Mon 9 Jul 07:52:45 2007|SETI@home|Starting 27fe00ab.6539.28922.915908.3.201_1
Mon 9 Jul 07:52:45 2007|SETI@home|Starting task 27fe00ab.6539.28922.915908.3.201_1 using setiathome_enhanced version 513
Mon 9 Jul 07:52:47 2007|SETI@home|[file_xfer] Started upload of file 27fe00ab.6539.32633.286082.3.228_1_0
Mon 9 Jul 07:52:51 2007|SETI@home|[file_xfer] Finished upload of file 27fe00ab.6539.32633.286082.3.228_1_0
Mon 9 Jul 07:52:51 2007|SETI@home|[file_xfer] Throughput 11767 bytes/sec
Mon 9 Jul 07:52:55 2007|SETI@home|Sending scheduler request: To report completed tasks
Mon 9 Jul 07:52:55 2007|SETI@home|Reporting 1 tasks
Mon 9 Jul 07:53:00 2007|SETI@home|Scheduler RPC succeeded [server version 509]
Mon 9 Jul 07:53:00 2007|SETI@home|Deferring communication for 11 sec
Mon 9 Jul 07:53:00 2007|SETI@home|Reason: requested by project
Mon 9 Jul 07:53:15 2007|SETI@home|Sending scheduler request: To report completed tasks
Mon 9 Jul 07:53:15 2007|SETI@home|Reporting 2 tasks
Mon 9 Jul 07:53:20 2007|SETI@home|Scheduler RPC succeeded [server version 509]
Mon 9 Jul 07:53:20 2007|SETI@home|Deferring communication for 11 sec
Mon 9 Jul 07:53:20 2007|SETI@home|Reason: requested by project
Mon 9 Jul 08:42:47 2007|SETI@home|Computation for task 27fe00ab.6539.28776.897148.3.201_1 finished
Mon 9 Jul 08:42:47 2007|SETI@home|Starting 10jn00aa.2104.4784.815902.3.91_0
Mon 9 Jul 08:42:47 2007|SETI@home|Starting task 10jn00aa.2104.4784.815902.3.91_0 using setiathome_enhanced version 513
Mon 9 Jul 08:42:49 2007|SETI@home|[file_xfer] Started upload of file 27fe00ab.6539.28776.897148.3.201_1_0
Mon 9 Jul 08:42:52 2007|SETI@home|[file_xfer] Finished upload of file 27fe00ab.6539.28776.897148.3.201_1_0
Mon 9 Jul 08:42:52 2007|SETI@home|[file_xfer] Throughput 10918 bytes/sec
Mon 9 Jul 08:42:56 2007|SETI@home|Sending scheduler request: To report completed tasks
Mon 9 Jul 08:42:56 2007|SETI@home|Reporting 1 tasks
Mon 9 Jul 08:43:01 2007|SETI@home|Scheduler RPC succeeded [server version 509]
Mon 9 Jul 08:43:01 2007|SETI@home|Deferring communication for 11 sec
Mon 9 Jul 08:43:01 2007|SETI@home|Reason: requested by project
Mon 9 Jul 08:43:16 2007|SETI@home|Sending scheduler request: To report completed tasks
Mon 9 Jul 08:43:16 2007|SETI@home|Reporting 3 tasks
Mon 9 Jul 08:43:21 2007|SETI@home|Scheduler RPC succeeded [server version 509]
Mon 9 Jul 08:43:21 2007|SETI@home|Deferring communication for 11 sec
Mon 9 Jul 08:43:21 2007|SETI@home|Reason: requested by project
Mon 9 Jul 09:08:08 2007|SETI@home|Starting 03mr00aa.283.31329.754822.3.199_2
Mon 9 Jul 09:08:08 2007|SETI@home|Starting task 03mr00aa.283.31329.754822.3.199_2 using setiathome_enhanced version 513
Mon 9 Jul 09:08:14 2007|SETI@home|Starting 12jn00aa.7220.23938.779818.3.39_0
Mon 9 Jul 09:08:14 2007|SETI@home|Starting task 12jn00aa.7220.23938.779818.3.39_0 using setiathome_enhanced version 513
Mon 9 Jul 09:08:23 2007|SETI@home|Starting 12jn00aa.7220.14849.29822.3.181_0
Mon 9 Jul 09:08:23 2007|SETI@home|Starting task 12jn00aa.7220.14849.29822.3.181_0 using setiathome_enhanced version 513
Mon 9 Jul 09:08:27 2007|SETI@home|Starting 11jn00aa.26574.20705.192314.3.18_0
Mon 9 Jul 09:08:28 2007|SETI@home|Starting task 11jn00aa.26574.20705.192314.3.18_0 using setiathome_enhanced version 513
Mon 9 Jul 09:08:35 2007|SETI@home|Starting 03mr00aa.283.33201.317312.3.45_1
Mon 9 Jul 09:08:35 2007|SETI@home|Starting task 03mr00aa.283.33201.317312.3.45_1 using setiathome_enhanced version 513
Mon 9 Jul 09:08:54 2007|SETI@home|Starting 10jn00aa.2104.976.47148.3.48_1
Mon 9 Jul 09:08:54 2007|SETI@home|Starting task 10jn00aa.2104.976.47148.3.48_1 using setiathome_enhanced version 513
Mon 9 Jul 09:09:05 2007|SETI@home|Starting 12jn00aa.7220.27968.3394.3.37_2
Mon 9 Jul 09:09:05 2007|SETI@home|Starting task 12jn00aa.7220.27968.3394.3.37_2 using setiathome_enhanced version 513
Mon 9 Jul 09:09:12 2007|SETI@home|Starting 12jn00aa.7220.28114.48580.3.69_1
Mon 9 Jul 09:09:14 2007|SETI@home|Starting task 12jn00aa.7220.28114.48580.3.69_1 using setiathome_enhanced version 513
Mon 9 Jul 09:09:19 2007|SETI@home|Starting 12jn00aa.7220.20225.386062.3.120_2
Mon 9 Jul 09:09:20 2007|SETI@home|Starting 12jn00aa.7220.28882.990916.3.13_2
Mon 9 Jul 09:09:56 2007|SETI@home|Starting 12jn00aa.7220.29696.565904.3.74_0
Mon 9 Jul 09:10:01 2007|SETI@home|Starting 10jn00ab.1781.4737.104832.3.162_2
Mon 9 Jul 09:10:18 2007|SETI@home|Starting 10jn00ab.1781.4737.104832.3.162_2
Mon 9 Jul 09:10:18 2007|SETI@home|Starting 09jn00aa.4199.1792.665884.3.255_1
Mon 9 Jul 09:10:56 2007|SETI@home|Resuming task 11jn00aa.26574.20705.192314.3.18_0 using setiathome_enhanced version 513

No tasks have been lost after "resuming" all the previously "suspended" tasks, but the "Waiting for shared memory" status apparently awaiting in the queue just like "Ready to Start" and "Waiting to Run".

Hope this information may help your looking into these memory problems. It may be worth mentioning that when I suspended a similar number of tasks in an older BOINC version at least 4 months ago, all the tasks were marked off as "Computation error" and were lost even if they had some crunching time accrued.

Keith

It could also be, that the parameters "Use at most Enforced by version 5.8 and greater XX % of memory when computer is in use" and "Use at most Enforced by version 5.8 and greater 90% of memory when computer is idle" should be set higher at the SETI homepage. With this changes, the BOINC client restrict the usage of the memory.
But, I recommend you to set up the shared memory parameters, as Zombie has written, too.

---