A few of the updates which I have pushed recently:

• I did away with check-pointing entirely for now. I would like to have it, but for now seemed more trouble that its worth. This should solve many memory / disk space / stuck job problems some were seeing.
  
• I shortened the jobs (~20min on my laptop) so they're shorter and there's less need for check-pointing anyway.
  
• The server status page has a link to the exact version of the code which the server is currently running, for those curious.
  
• No more camb_legacy jobs should be sneaking in if your host can run camb_boinc2docker.
  

boboviz, did you use a different username on the beta server? I can't find your jobs, but if they're able to crash your computer I'd like to take a look at them right away!

Do you still see it happen if you lower your BOINC CPU usage to say 50%?

I played with that option, but suspend/resume still seemed very unstable. Plenty of times it seemed I got into a state where the task just hung indefinitely, restarted anyway, etc... Conversely the current setup has seemed very robust based on results I'm seeing on the beta server. The only drawback is, as you say, having to start over. At least the jobs are very short so you're not losing too much work.

For now I'm going to launch with the current setup. Eventually I think <enable_vm_savestate_usage/> is definitely the way to go, but after a little more debugging.

So do I understand correctly, you edited the vbox_job.xml file to add <enable_vmsavestate/>? I'm confused though because in http://beta.cosmologyathome.org/result.php?resultid=41172 I see no mention of saving state in the log? In any case, I lowered the disk bound since without checkpointing it wasn't necessary.

My tests.
As Marius says, i start with cpu time usage at 50% and slowly pass to 60, 70, 80.... and so on. At 75% my pc starts to lag. At 85% crashes. Temperature is near to limit (83°), but if i crunch Rosetta@home (that stresses very well the cpu) at 100% i have no problem.
My cpu is a AMD FX6300 with stock dissipation.
This is the ONLY project i have these problems. It's an atomic application!!! :-)

I think generally I don't completely understand the experience people are having with the camb_boinc2docker app who also run other projects concurrently, since I myself am testing only with C@H. Maybe some of you could explain a bit more how you would like things to run vs. how they do run?

* Restrict the number of active CPU cores per host, defaulting to (maybe) one half, configurable on the pref page
* Work with the VBOX Wrapper authors to set the CPU Priorities to "lower than default".

Without it this project wipes out most other uses of the computer on which it is running.

On the new Cosmology@Home website, how can I log off or log out of the current account? I manage a few different BOINC accounts, but I don't see any option to log off or log out on Firefox, like I do on my other BOINC projects.

Am I missing something, or did you forget to implement it?

Hello,

Had to abort this WU after 7h10 running time :/

http://www.cosmologyathome.org/result.php?resultid=34122249

Would it be possible to add an automatic "abandon" function ?

ie after x minutes.

Thank You

Best

Phil1966

Dear Marius,

Thank You for your answer.

Just had another one last night (> 8 hours) : http://www.cosmologyathome.org/result.php?resultid=34122301

Best Regards,

Phil1966

I stop crunching these WU's. There is maybe something wrong with my crunchbox.

The first one I launched tonight was still running after 48 minutes => manual abandon.

Back to camb_legacy.

Phil1966

I recall seeing someone mention problems with VirtualBox 4.3.12. I would try VirtualBox 5.0.8.
https://www.virtualbox.org/wiki/Downloads

Hello Jim348,

VirtualBox 5 was installed on my crunchbox, but as it was not working
when runing C@H, I re-installed the standard 4.3.12 version.

Will give another try this evening.

Thank You.

Hi Phil1966, hmm thanks for pointing me to this, these jobs hanging after the computation is over ...