Aborted this one, took about 25 min to get to 0.13% completed.

LINK to unit

- Unhandled Exception Record -
Reason: Breakpoint Encountered (0x80000003) at address 0x7C901230

Is there a certain time limit built in whare they will stop by themselves if not being watched?

Was thinking of running this program on another computer that I only get to see about one time a week. Would hate to have it go a coupple days like that.

---

I am seeing a possibly related issue. When a WU executes past it's estimated running time, it resets the time to complete. At this point, the progress indicator increases very little and the time to complete increases slowly. However, within a minute or two (wallclock time) the WU finishes. THe problem seems cosmetic, but I really can't tell.

Jim

I am seeing a possibly related issue. When a WU executes past it's estimated running time, it resets the time to complete. At this point, the progress indicator increases very little and the time to complete increases slowly. However, within a minute or two (wallclock time) the WU finishes. THe problem seems cosmetic, but I really can't tell.

Jim

Mine has the same issue. I thought it was weird, then I stopped crunching and released the workunit from the memory. Though it was restarted the workunit hardly progressed and seemed almost stuck. Any idea?

suguruhirahara

---

As mentioned in other threads, the WU will progress to 100% then the percent complete will reset and count up slowly to about .150%. The first part is the WU crunching and the reset does some kind of internal validation or something. Anyway it is perfectly normal for this to happen.

There are issues right now of WUs not d/l properly and clogging the system.

---

As mentioned in other threads, the WU will progress to 100% then the percent complete will reset and count up slowly to about .150%. The first part is the WU crunching and the reset does some kind of internal validation or something. Anyway it is perfectly normal for this to happen.

There are issues right now of WUs not d/l properly and clogging the system.

Sounds good. I have not seen the d/l issues, but then, I only joined today.

Jim

As mentioned in other threads, the WU will progress to 100% then the percent complete will reset and count up slowly to about .150%. The first part is the WU crunching and the reset does some kind of internal validation or something. Anyway it is perfectly normal for this to happen.

There are issues right now of WUs not d/l properly and clogging the system.

Sounds good. I have not seen the d/l issues, but then, I only joined today.

Jim

Some of them seem to be missing a file. This somehow causes the system to stop d/l new WUs. If you get one abort the WU (Task Tab) and the transfer file (transfer tab in BOINC Manager).

Anyway welcome to the MW@H! Try not to get frustrated with the errors that we run into and know that it is an Alpha project and therefore will have problems.

Acmefrog

---

Hi,

....If you get one abort the WU (Task Tab) and the transfer file (transfer tab in BOINC Manager).

You only actually need to abort the transfer, the WU will be automatically aborted when you do this.


TTFN - Pete.

---