8.86 Holding 4 Threads with Scheduler
in Bugs

15:12 (time in the screenshot) was 25 minutes ago and it's just sitting and not releasing those threads so the scheduler can continue.
Comments
Can you replicate this?
I usually got those errors when I stop the projects after an out of memory message.
@sven I can give you project backups or logs, or even a video i that would help.
This bug blocks the project, only option is to restart the program. Alot of times, I had to end taks because the program could not be closed because of this error.
I can see this affecting people who use scripts to automate ser as well.
Sven is the expert but I don't see this as that big of a deal. I deal with this multiple times per day on our dedicated servers as I'm constantly stopping and starting the scheduler to add new projects in. I would say on our boxes that run 1000+ threads I have to force close SER about 25% of the time. No big deal, takes care of things quickly and you get a nice clean instance to fire back up again. I can see @cefege point about the scripting though...
I want to try to go back to the previous version of Ser (the 8.85) to see if it fix this problem, but I don't remember how to go back to the last version.... I remember there is a way but I can't remember it now....
Any help please?
So it's not a problem of the 8.86 version :-(
Do you have the 8.84 version please?
My threads number was 1 since 2 days, today I tried to uncheck the 2 boxes:
- Automatically decrease threads on a CPU usage.... and
- Automatically decrease threads on a Memory usage....
and now I'm having the same 240 threads working as before!!