I have noticed that since I have upgraded to BOINC 5.2.x that my projects are being removed from memory when preempted, even though I have the option set to leave them in memory under the general preferences.

Any idea why this might be occuring?

using windows XP, 383 MB Ram, 1.0 ghz,

running CPDN, Einstein, LHC, and WCG all together.

recently increased my diskspace allowed to 2 Gb for BOINC....

not sure if other settings need adjusting.........the option was working prior to the upgrade though.

Another weird thing that started happening was that when I go to view graphics for CPDN, BOINC asks me if I really want to do this for a "remote location", but I only have one location.......can't think of anything I have changed to cause this either.......

Another weird thing that started happening was that when I go to view graphics for CPDN, BOINC asks me if I really want to do this for a "remote location", but I only have one location.......can't think of anything I have changed to cause this either.......

NO idea on "leave in memory" - works fine for me, all versions. The "remote graphics" bug is the one that was fixed in V5.2.12, after having appeared somewhere around 5.2.10.

---

Thanks for the tip on the "remote graphics" bug.......downloading 5.2.12 cleared that up as expected...

projects are still being removed from memory though.......

not a major problem for the projects except CPDN.....

don't know what to do though...

Slightly OT:
I'm running 5.2.8, and the Remote Graphics bug is in this version.

projects are still being removed from memory though.......

Just to be sure it's a version problem and not a preferences problem... can you go to a different project than where you set that preference, change "something else minor" if "leave in memory" is already "yes" (obviously, change "no" to "yes" on that instead, if it's set wrong) and save on the website, then go back to BOINC Manager and hit "Update" for the project you just changed? That will hopefully insure that your local host has the changed setting. If it still doesn't leave the apps in memory, we'll probably have to get a developer to take a look at it.

---

Sorry, I only run cpdn. And it IS set for "Leave in memory=Yes".
I went to 5.2.8 to run Spinup, and can live with slight problem.
Apparently, this sub-project has a problem near the 50 year boundary, so I'll backup just before, and upgrade to whatever is around then.

Anyone else listening who wants to test "Leave in memory=Yes"?

Sorry, I only run cpdn. And it IS set for "Leave in memory=Yes".

My response was to the thread owner, who said "running CPDN, Einstein, LHC, and WCG all together." - this is why I quoted from his last message, to clarify who I was speaking to.

Do you also have the "leave in memory" problem? All you have said is that the "remote computer" problem was in 5.2.8, and we know the answer to that one. It is unrelated to the thread topic, that was a side question.

---

My apologies. I waited overnight, but no one else responded.
I don't know if I have the leave in memory problem, and I'm not going to push my luck.

OK, I went into LHC@home account and fiddled around with some of my disk usage settings,....increased them a bit........and did an update.........leave in memory was already set to yes.

So, I'll keep an eye out for the next switch and see what happens.

only thing of note is that after performing the update I get this...which to me seems normal....but may be helpful.

11/29/2005 5:34:34 PM|LHC@home|General preferences have been updated
11/29/2005 5:34:34 PM||General prefs: from LHC@home (last modified 2005-11-29 17:34:23)
11/29/2005 5:34:34 PM||General prefs: using separate prefs for home

the "using separate prefs for home" made me wonder, but I kind of assumed this was the default. I haven't ever messed with the at school prefs, or work ones, as I only have one PC.

Well, until yesterday......I just set up the one at the parents, I'll ask what that one is doing to compare, it should be using my preferences since it's running under my account.

Ok, the seperate prefs at home was the trick...........didn't notice that on the main general prefs page that there is what looks like a default group of settings, and then down below that are the same options for "home".......under those options, leave in memory was set to no..........I've fixed that and am assuming that will fix things.....

figured I was just overlooking something..........I know better now!

thanks for working through this with me.

Ok, the seperate prefs at home was the trick

Great! Much better to be a "single user" issue than a bug that'd start affecting everyone... Thanks very much for reporting back that it has been solved.

---