Hi

The Python tasks have been working ok until 18th Sept, and I watch the percentage rise over the day and normally complete over night, but not after the 18th Sept and the Task results state EOFERROR when I look at the task info.

Also I see this in the Dump info multiple times about Memory Leaks:
Everything is Ok

Files: 18281
Size: 4951763651
Compressed: 4965969920
16:34:28 (36040): .\7za.exe exited; CPU time 49.953125
16:34:28 (36040): wrapper: running python.exe (run.py)
Starting!!
Windows fix!!
Define rollouts storage
Define scheme
Created CWorker with worker_index 0
Created GWorker with worker_index 0
Created UWorker with worker_index 0
Created training scheme.
Define learner
Created Learner.
Detected memory leaks!
Dumping objects ->
..\api\boinc_api.cpp(309) : {11145} normal block at 0x0000028CD42A38F0, 8 bytes long.
Data: < ' > 00 00 27 D4 8C 02 00 00
..\lib\diagnostics_win.cpp(417) : {9641} normal block at 0x0000028CD42A5580, 1080 bytes long.
Data: < ^ $ > F0 5E 00 00 CD CD CD CD 24 01 00 00 00 00 00 00
..\zip\boinc_zip.cpp(122) : {400} normal block at 0x0000028CD42A1F90, 260 bytes long.
Data: < > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
{386} normal block at 0x0000028CD429D3E0, 52 bytes long.
Data: < r > 01 00 00 00 72 00 CD CD 00 00 00 00 00 00 00 00
{381} normal block at 0x0000028CD429D300, 43 bytes long.
Data: < p > 01 00 00 00 70 00 CD CD 00 00 00 00 00 00 00 00
{376} normal block at 0x0000028CD429D290, 44 bytes long.
Data: < ) > 01 00 00 00 00 00 CD CD B1 D2 29 D4 8C 02 00 00
{371} normal block at 0x0000028CD429D5A0, 44 bytes long.
Data: < ) > 01 00 00 00 00 00 CD CD C1 D5 29 D4 8C 02 00 00
Object dump complete.

What's going on ?

Kim

I believe that is all normal for Window users.

The Detected memory leaks! happens when you stop and restart tasks. It should continue to run ok unless you are having other issues.

I quickly checked through your tasks and all of them since September 12th have failed. Many of them have multiple stops and restarts.

Best practice is to leave the tasks running until completion. If you stop and restart them too many times they tend to fail.

All of the ones which failed actually appear to have a common failure mode that hasn't been addressed yet.

You may have just been very unlucky to have all bad tasks but leave the next one running until completion and check the stderr for other issues.

Thanks for the help.

Will leave for a day and see what happens.

The main issue is that this is my working PC so it gets stopped at least 4 times a day.

Kim

Probably you have just been unlucky to get a bad, malformed work unit.

I see I have a couple of early exit, EOFerror tasks now.

Nothing wrong with your equipment or system likely.