That is a failed assertion inside the Xojo runtime library, not an exception. It is a Xojo bug. There is no way for you to handle it, though you could possibly work around it if you were to able to figure out what is causing it.
This one should be handled with priority since this makes me feeling insecure about stability of released software. Think Xojo R&D and Sascha should collaborate in researching this one, before it gets a big problem outside.
I would like to, but it’s totally random and i see it in a project which won’t run except in our Company Intranet/VPN + i am not allowed to give it away.
[quote=112712:@Sascha S]Yes. I have a few Threads running.
But i am VERY carefully monitoring that each Thread is only running as short as possible and ended gracefully.[/quote]
Can you say more about how you monitor them, and how you end them? Perhaps it’s something in the way you are doing those options.
I have 2 global properties. One is a counter which is increased anytime a Thread starts and decreased when this Thread ends. The second is a boolean property which is set to True when the user is quitting the app.
Each Thread is monitoring the boolean. If the boolean goes to True while such a Thread is running, the Thread exits.
A timer in the Main Window is checking if the Thread counter gone to 0 before the App is closing/quitting.
2 Threads running periodically in the Background. One is monitoring important network resources (Database Servers, Webservers, …) the other is querying a mySQL Database to pull Data. All other Threads are only running by “users request”.