When many long experiments (>200 iterations) are run sequentially on a single instance of cspy, cspy tends to crash. It then provides no traceback on the issue.
During the last crash I experienced I found the error log in the Windows Error viewer. The error info is as follows:
Faulting application name: python.exe, version: 0.0.0.0, time stamp: 0x5c7c8191
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x4274
Faulting application start time: 0x01d7da60b3c02411
Faulting application path: C:\Users\Hybrid\Envs\cspy\Scripts\python.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 8cc03547-34c0-4841-b359-aa0c6826ceda
Faulting package full name:
Faulting package-relative application ID:
A brief search online indicates that the issue could be a couple of things:
When many long experiments (>200 iterations) are run sequentially on a single instance of cspy, cspy tends to crash. It then provides no traceback on the issue.
During the last crash I experienced I found the error log in the Windows Error viewer. The error info is as follows: Faulting application name: python.exe, version: 0.0.0.0, time stamp: 0x5c7c8191 Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6 Exception code: 0xc0000374 Fault offset: 0x00000000000ff199 Faulting process id: 0x4274 Faulting application start time: 0x01d7da60b3c02411 Faulting application path: C:\Users\Hybrid\Envs\cspy\Scripts\python.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 8cc03547-34c0-4841-b359-aa0c6826ceda Faulting package full name: Faulting package-relative application ID:
A brief search online indicates that the issue could be a couple of things: