i'm not exactly sure if Sven has added the CMS -> Drupal captcha to CB in the latest version which may cause some issues because it is very slow (= high CPU).
i have an optimized version for that which is much faster.
It crashes consistently for us too now - on over 6 servers. Not sure what's happening - but SER stops responding after 1-2 minutes
Basically, we cant access the SER window anymore - it becomes either completely black, or just unresponsive - happened after the CB update to 1.87 the first time (might be correlated, might not..)
Also, I think Ozz might be on a right track here. As everytime the SER window freezes its when CB is solving a drupal captcha and it takes CB around 8-10 seconds for that one.
Sven, as I mentioned a bit earlier in this thread. I had the black freezing window when I updated to 5.82. The scheduler was also freezing if I tried to manually stop it. I rolled back from 5.82 to 5.81 and it has been running for two days with no problems. I think the bug arrived between 5.81 and 5.82 if it helps you at all.
rename the actual .exe or the _old.exe according to its version number and safe it to your installation folder.
for the actual release copy and rename it to "Search Engine Ranker v5.86.exe" for example. when you like to run v5.86 again than just start SER with that exe.
Checked this morning and SER ran fine through the night. I tried to stop the scheduler and it still gets stuck with 5.86 - just shows wait on the stop button and never ends.
Looks like an improvement but there is still something with stopping the scheduler as 5.81 stopped it perfectly?
Comments
How can we rolling back to previous version?
Basically, we cant access the SER window anymore - it becomes either completely black, or just unresponsive - happened after the CB update to 1.87 the first time (might be correlated, might not..)
Also, I think Ozz might be on a right track here. As everytime the SER window freezes its when CB is solving a drupal captcha and it takes CB around 8-10 seconds for that one.
Looks like an improvement but there is still something with stopping the scheduler as 5.81 stopped it perfectly?