I have had this happen for a long time, it's quite rare however and random. Can you replicate this? I usually got those errors when I stop the projects after an out of memory message.
Well thats actually the problem of a OOM (oh new short term) error. You never know where this occurs and everything on this thread is lost...even a signal to the main thread that this one is over.
@sven so what are we supposed to do? 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.
Having SER force close threads is a great way to cause a BSOD. I can't tell you how many times I have a full crash due to doing a stop operation in one of our active GScraper instances.
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...
cefege the only option would be to stop it from causing the out of memory issue...and that can be done in lowering threads, using less content for projects or starting less projects at once.
I have the same problem since today.... only 1 thread running while I set it up to 180 threads as always since months.
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?
Mmm.... I have found it (it was the file Search_Engine_Ranker_old.exe, on c:\program), I installed it, and now the threads changed from 1 to.... 80, later 60, later 15, at the moment 5.... and it's going lower and lower..
@sven@peterperseo I'm running 8.84 and don't have the issue anymore. I still get the normal OOM errors which I always get because I push my servers to the limit, but the problem of retaining threads is not there in 8.84.
I solved the trouble!! 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!!
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!!