I’ve created a test case on Windows 64bit - as a Worker, compiled to an EXE. The App is copying thousands of files - 50 megs to 4 gigs. I find that once the Disk I/O becomes saturated (queued I/O), if the App is force closed or crashes, the 4 Workers will become orphaned and never close, even though their parent App is gone. The 4 Workers will bring the 8 core system to near 100% CPU load and it will not stop unless the Task Manager is used to Force Quit the 4 Workers.
I submitted a Bug Report with a Link to a Video and Test Files. XoJo Support says they can not reproduce this issue and closed the Bug Report.
I’m hoping other members of the Forum will download my Test Apps and Video and attempt to reproduce this for themselves so that I can have XoJo reopen this Bug Report.
The Link includes a sample PNG (42 megs) and a simple App to create 50 copies in a folder. The second App is the XoJo PictureResizer Worker Sample with some minor changes. I’ve keep the Output at 100% size to produce more Disk I/O. I set a marker below the Progress Bar where it suggest that the Force Quit (Red X at the Top right) is to be clicked to force Quit the App.
If more disk I/O is needed, change the File Copy App to make 100 copies (source included).
When testing, be sure to compile to a Windows 64 bit EXE. This will not fail as a Debug Run since the Workers are run as Threads in Debug-Run mode.
Thanks for your help.