This forum contains information about 3rd party applications which may be of use to those who run the FAH client and one place where you might be able to get help when using one of those apps.
toTOW wrote:FAHmon beta2 crashed when I finished a p2619 (A2 core) ... (it was a gen 3 WU ... completition was at 400%)
I was unable to restart FAHmon unless it gets a new WU (it got a 2653).
This should be fixed now. The code added to cope with the % completion issues was interpreting 400% as 0% and it caused a divide by zero error.
I've got around this by always interpreting 200%,300%,400% etc. as 100%. This will of course make the first frame of one of these WUs appear to be at 100% but that can't easily be avoided and shouldn't cause any non-cosmetic issues.
toTOW wrote:FAHmon beta2 crashed when I finished a p2619 (A2 core) ... (it was a gen 3 WU ... completition was at 400%)
I was unable to restart FAHmon unless it gets a new WU (it got a 2653).
This should be fixed now. The code added to cope with the % completion issues was interpreting 400% as 0% and it caused a divide by zero error.
I've got around this by always interpreting 200%,300%,400% etc. as 100%. This will of course make the first frame of one of these WUs appear to be at 100% but that can't easily be avoided and shouldn't cause any non-cosmetic issues.
Is there a reason why you're not using the values of step xxx of yyy rather than the reported percentage?
toTOW wrote:FAHmon beta2 crashed when I finished a p2619 (A2 core) ... (it was a gen 3 WU ... completition was at 400%)
I was unable to restart FAHmon unless it gets a new WU (it got a 2653).
This should be fixed now. The code added to cope with the % completion issues was interpreting 400% as 0% and it caused a divide by zero error.
I've got around this by always interpreting 200%,300%,400% etc. as 100%. This will of course make the first frame of one of these WUs appear to be at 100% but that can't easily be avoided and shouldn't cause any non-cosmetic issues.
Is there a reason why you're not using the values of step xxx of yyy rather than the reported percentage?
Yes, it's not reliable for certain log files (smp messy fahlog output) and missing entirely for other logs (core_10, some versions of core_7b).
toTOW wrote:FAHmon beta2 crashed when I finished a p2619 (A2 core) ... (it was a gen 3 WU ... completition was at 400%)
I was unable to restart FAHmon unless it gets a new WU (it got a 2653).
Hmm, thats not good. I added some code to try and cope with the % completion issues, which may be the cause, I don't know. The 2619's I've had recently have all been gen 0.
I'm folding a Gen 1 atm ... I'll check if FAHmon crashes again at 200% or not
Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
