Posts by mdillenk

1) Message boards : Number crunching : Jobs lock up and never finish (Message 65308) Posted 13 Feb 2010 by mdillenk Post: I had this problem as well, nothing really helped. It looked a bit like a RAM issue or just "another application issue" - the WU was being heavier and heavier crunched and in some moment, i.e. switching to some app, killing the browser etc. - this happens. For me it was like a quiet BOINC/Rosetta crash. That was a final straw for me for some time. I'll wait with Rosetta till some new WUs or a new computer, preferably. :) Rosie seems to want more than I can always provide. My latest tweak has been to turn max allowed memory use up to 90% when the computer is in use. By default it is 90% for when the computer is idle so I turned it up to 90% for when it is in use as well. One of the jobs that froze took up 500 megs of RAM when I restarted it, so maybe the client is freezing the job because it's taking up too much memory when the computer goes from "idle" to "in use".
2) Message boards : Number crunching : Jobs lock up and never finish (Message 65256) Posted 10 Feb 2010 by mdillenk Post: Do the people with this issue see the wu start and then "freeze" or do they never really start? It appears that they actually do start. They progress, percentage increases, during which they are utilizing CPU. Then when I check on it the time to completion number has gone up to 8 10 or more hours and the time running is way over the normal 3-3 1/2 hours to completion. Task manager shows that job is in memory but not utilizing any CPU. I wonder if it's an issue with anti-virus, however my anti-virus program isn't giving me any warnings.
3) Message boards : Number crunching : Jobs lock up and never finish (Message 65241) Posted 8 Feb 2010 by mdillenk Post: Jobs such as these never finished, in the BOINC client they look frozen but the job doesn't utilize any cpu I have had a few of these. I find that if you either suspend that work unit and then reactivate it, or exit BOINC and restart. The work unit then usually competes normally. I'll try restarting the client and see, in the past I've just aborted the frozen task and let the next one in the queue kick off. I've upgraded to the 6.10.32 client and haven't seen a problem again yet, I'll keep my fingers crossed. The 6.10.32 client still has the same problem. Restarting the client does make the frozen jobs continue progress but I've had jobs that I have to reset the client for several times before they finish. It would be cool if the client could detect this problem and take the appropriate "reset" action to make the job continue progress.
4) Message boards : Number crunching : Jobs lock up and never finish (Message 65212) Posted 5 Feb 2010 by mdillenk Post: Jobs such as these never finished, in the BOINC client they look frozen but the job doesn't utilize any cpu I have had a few of these. I find that if you either suspend that work unit and then reactivate it, or exit BOINC and restart. The work unit then usually competes normally. I'll try restarting the client and see, in the past I've just aborted the frozen task and let the next one in the queue kick off. I've upgraded to the 6.10.32 client and haven't seen a problem again yet, I'll keep my fingers crossed.
5) Message boards : Number crunching : Jobs lock up and never finish (Message 65209) Posted 4 Feb 2010 by mdillenk Post: Jobs such as these never finished, in the BOINC client they look frozen but the job doesn't utilize any cpu I have had a few of these. I find that if you either suspend that work unit and then reactivate it, or exit BOINC and restart. The work unit then usually competes normally. I'll try restarting the client and see, in the past I've just aborted the frozen task and let the next one in the queue kick off.
6) Questions and Answers : Windows : Frequent hung work units (Message 65200) Posted 4 Feb 2010 by mdillenk Post: I find it difficult to believe that more people aren't having this problem. This is happening on two totally fresh/vanilla installs of BOINC with Rosetta@home as the only running science app. I'm having the same exact problem: Jobs such as these never finished, in the BOINC client they look frozen but the job doesn't utilize any cpu. I would guess that between 5% to 10% of the jobs do this. I'm running the 64 bit BOINC client on Windows 7 64. Any body else having problems like this or know what may be wrong? t374__boinc_filtered_loopbuild_threading_cst_lb_tex_IGNORE_THE_REST_16900_5733_0 t365__boinc_filtered_loopbuild_threading_cst_all_tex_IGNORE_THE_REST_16902_5996_0 lr15clus_opt_.1eyv.1eyv.IGNORE_THE_REST.c.10.2.pdb.pdb.JOB_17448_1_0
7) Questions and Answers : Windows : Problems with jobs not finishing, they freeze seemingly randomly (Message 65197) Posted 4 Feb 2010 by mdillenk Post: Jobs such as these never finished, in the BOINC client they look frozen but the job doesn't utilize any cpu. I would guess that between 5% to 10% of the jobs do this. I'm running the latest stable 64 bit BOINC client on Windows 7 64. Any body else having problems like this or know what may be wrong? CPU is Intel Wolfdale E8400. t374__boinc_filtered_loopbuild_threading_cst_lb_tex_IGNORE_THE_REST_16900_5733_0 t365__boinc_filtered_loopbuild_threading_cst_all_tex_IGNORE_THE_REST_16902_5996_0 lr15clus_opt_.1eyv.1eyv.IGNORE_THE_REST.c.10.2.pdb.pdb.JOB_17448_1_0
8) Message boards : Number crunching : Jobs lock up and never finish (Message 65196) Posted 4 Feb 2010 by mdillenk Post: Jobs such as these never finished, in the BOINC client they look frozen but the job doesn't utilize any cpu. I would guess that between 5% to 10% of the jobs do this. I'm running the 64 bit BOINC client on Windows 7 64. Any body else having problems like this or know what may be wrong? t374__boinc_filtered_loopbuild_threading_cst_lb_tex_IGNORE_THE_REST_16900_5733_0 t365__boinc_filtered_loopbuild_threading_cst_all_tex_IGNORE_THE_REST_16902_5996_0 lr15clus_opt_.1eyv.1eyv.IGNORE_THE_REST.c.10.2.pdb.pdb.JOB_17448_1_0