I have a client running my Mac/Win desktop app on Windows 11. He has two systems where my app from the front end looks like it hangs for a feature that uses a worker. This app was released over a year ago and I haven’t had anyone else report this error, which is a core feature.
Over the last week I’ve sent him special builds of my app which creates a log file to the desktop. The worker is launched (.start called) from a thread. The worker has .CorePercent = 90 and .MaxCoreCount = 128. Execution of the thread is logged before and after worker.start. However, the same log file contains absolutely nothing from the worker itself, including the start of the JobRequested event handler. I’ve tested the same app on my Windows 11 system and all works fine.
Does anyone have an idea what may be stopping my app from launching its worker on these client systems on Windows 11? The client is very helpful so I can build a small test app for him to run. Apart from creating log file calls around the worker start and from within the worker as I’ve done with my production app, is there anything else I can check for? In case there’s a write permission issue from the worker, is there a better way to log from a worker that doesn’t require a lot of work for my client? Are there any security apps or Windows settings that can stop a worker from launching?
App built with Xojo 2025r3.
Many thanks, Mark