| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000190 | Rosetta | [All Projects] Bad Coding | public | 2013-03-01 10:57 | 2015-08-18 11:13 |
|
| Reporter | smlewis | |
| Assigned To | | |
| Priority | normal | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | | |
| Fixed in Version | | |
|
| Summary | 0000190: -jd2:delete_old_poses and JD2 memory leak |
| Description | JD2 has a longstanding memory leak that becomes quite serious in a large -l environment. "Old poses" - inputs that Rosetta is through with and will not reuse - are maintained in memory.
The flag -jd2:delete_old_poses prevents this memory leak but affects Oliver's code for reloading results into the JobDistributor as new jobs, and may affect RosettaScripts due to modification of Poses before distribution starts. |
| Additional Information | We'd love to turn the flag on by default, so that Rosetta does not leak memory. What code will have a problem with this, and can this code be run with -jd2:delete_old_poses false, or be fixed directly?
A) Oliver's code?
B) RosettaScripts? |
| Tags | memory overload, Minicon_2013_defaults, robust_rosetta |
|
| Application(s) Affected | all jd2 |
| Command Line Used | jd2memtest -l pdblist, where pdblist is large - watch the memory usage climb |
| Developer Options | |
| Fixed in SVN Version | |
|
| Attached Files | |
|
Relationships 
Relationships