| Author | Message |
|---|
|
|
|
Another internal bugfix. A feature had been accidentally switched off.
Please post bug reports here, thanks ! |
|
|
|
|
|
A new version?
No wu, no debug.... :-) |
|
|
|
|
|
Lots of ha_notyr29Jan2010_3gbn_****_ProteinInterfaceDesign_6Apr2010_14587_1_0 work units fail with a segmentation violation on x86_64 Linux, e.g. http://ralph.bakerlab.org/result.php?resultid=1782249 |
|
|
|
|
Lots of ha_notyr29Jan2010_3gbn_****_ProteinInterfaceDesign_6Apr2010_14587_1_0 work units fail with a segmentation violation on x86_64 Linux, e.g. http://ralph.bakerlab.org/result.php?resultid=1782249
Same error on my Windows machines (1 error on each)
See 1783837
1783803
____________
 |
|
|
|
|
|
7gbnnotyr_3gbn work units tend to behave weird. They kinda get stuck 10 minutes to completion. Then it either jumps to 100% or stays at ~10 minutes to finish, but the progress bar is slowly advancing. I had pref time set to 4 hours, then i reduced it to 2 hours, but the magic 10 minutes is still the same.
Also i had one task (7gbnnotyr_3gbn) in that "10 minutes" phase, which i pressed "show graphics", which probably broke it. It was on model 873, step 187500 or 196500, something like that. 2 hours later it was on model 873, step 174500 os something like that, but continued slowly going up. I aborted this task.
This ha_notyr caught compute error. On www it says it was running for ~10 minutes, but in BOINC Manager it was shown as running for over 6 hours. It happened overnight, so i can't be sure what exactly happened there.
http://ralph.bakerlab.org/result.php?resultid=1782992
OS: WinXP 64
CPU: phenomII x4 945, NOT overclocked
RAM: 8GB
BOINC Manager was 6.10.37, now i updated to 6.10.43 to see if it helps anything ;)
____________
 |
|
|
|
|
|
New issue. I have BM set to keep applications in memory when switching. Now during the BM update the boinc service is shut down. During that shutdown all those remaining in memory applications are being closed. 2 of minirosetta_2.10_windows_x86_64.exe did not close during boinc shutdown and became orphaned in the system. Unfortunately i can't tell which WU they were crunching.
____________
|
|
|
|
|
|
1783989
Exit status -529697949 (0xffffffffe06d7363)
Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x753C9617
|
|
|
|
|
|
One task is running at 270 MB of real memory. Seems like a lot. Mac Core Duo OSX 10.4 |
|
|
|
|
|
270mb? Not a lot of memory...
In the past the wus used almost 900 mb of ram |
|
|
|
|
|
This task is using 361 MB of RAM which is fairly normal, what is not normal is the fact that the WU has been running for 22.12 Hours on a 6 hour preference has only gotten to 26.199% and has 32 Hours to go.
I am going to abort this WU
This WU
____________
|
|
|
|
|
|
An "old style" validate error on 1792938
|
|
|
