Community  
BROWSE SEARCH
Community Home
Advocacy
Help
Projects
Education
Development
GR Café

LOGIN
Email:
Password:
If you don't have an account,
click here to sign up.
DOCUMENTATION DISCUSSIONS FILE ROOM
Rosetta not releasing memory.

Rosetta not releasing memory.

 
ID: 71391
Posts: 1

I am using Progress through Processors via facebook. For some reason it does not release the memory upon suspend. I can watch in resource manager (Win7_64) as the CPU quiets down, but it maintains 6.5GB of memory, which is almost all my RAM. Even if I quit the app; exit as in not running, the rosetta threads remain and hold onto the memory. Should I just dump it and use Grid Repulics app? Its frustrating and I don't know where else to go for support.  
ID: 15261
Posts: 141

This is the place for support... are you still experiencing this issue?  We do not control the apps, but try to diagnose and relay the issue to the appropriate places.

I know that others were having some weird rosetta@home behavior, but I have not heard anything lately. 

ID: 74744
Posts: 1

I am currently having this issue. I have 2 computers connected one is running win7_64 and the other is winxp. Both have the issue where rosetta processes appear to never exit. Currently I have 33 "minirosetta_3.31_windows_x86_64" processes under boinc_project user each taking up ~400M of memory on my win7 machine. Any help debugging would be great. 

ID: 15261
Posts: 141

Hi Andrew,

This is happening very rarely and typically due to badwork units being sent out based on our previous experience.  We do not run the projects ourselves, but provide access to them.  The easiest thing you can do is reset the rosetta@home project and abort the current work units.  If this reappears suspend rosetta@home from getting new work for a while. 

ID: 5135
Posts: 2

Hi,

You can adjust the memory preferences in your user profile 

go to http://boinc.bakerlab.org/rosetta/prefs.php?subset=global

and edit the section  "Disk and memory usage"

Post   Previous   Page 1 of 1   Next
Please enable JavaScript support in Your web browser to display this page property.