Bugs in new version 2.10.10.0

[Deemer84]

Bugs, errors and problems in new version 2.10.10.0.

---

• Changelog
• Discussing version

---

 

[Bringomatix]

Seems I'm having very bad results with this new update
Getting a lot of timeouts and banned proxies

from 60% success rate I'm down to ...

https://drive.google.com/file/d/1caX2l3SctT_VDmb3-j40DKGuicMAeShQ/view?usp=drivesdk

 

[VladZen]

Seems I'm having very bad results with this new update
Getting a lot of timeouts and banned proxies

from 60% success rate I'm down to ...

https://drive.google.com/file/d/1caX2l3SctT_VDmb3-j40DKGuicMAeShQ/view?usp=drivesdk

You should disable protection in CapMonster settings>Protection. Then recognizing in 2.10.10 will work.

 

[Bringomatix]

This one?
https://drive.google.com/file/d/14I7xtLFRBm7GTZxpMakJntUV2Pxe0ceK/view?usp=drivesdk

 

[VladZen]

This one?
https://drive.google.com/file/d/14I7xtLFRBm7GTZxpMakJntUV2Pxe0ceK/view?usp=drivesdk

Yes...
But, we've already fixed it and you should just update modules in Update section in program settings and restart CapMonster.
Then recognizing should work with enabled protection.

 

[Bringomatix]

I upgraded, disabled protection and it started working okey
after a while ( a few hours), the received captcha went down from 1k per minute to 100 and a lot of timeouts

so the new version is still bugged.

I'm back to 2.10.9, that one seems to be working properly

 

[VladZen]

I upgraded, disabled protection and it started working okey
after a while ( a few hours), the received captcha went down from 1k per minute to 100 and a lot of timeouts

so the new version is still bugged.

I'm back to 2.10.9, that one seems to be working properly

I recommended you to update modules to fix the bug. Have you read that?

 

[Bringomatix]

did that before posting that message. it started working properly and after a few hours it went down completely

 

[VladZen]

did that before posting that message. it started working properly and after a few hours it went down completely

I think it's not a bug, it's over limit - 1k per minute. You'll get the same with 2.10.9.0.
What is method of solving by the way? Chrome is sitll recommended.

 

[Bringomatix]

I have 50 threads, its been stable at ~ 1k per minute for months ( same settings)
Using chrome, desktop proxy, rotating residential ones
https://drive.google.com/file/d/1sBaP1vsO09M3FT3MoPMOlmwJPfVqQlU4/view?usp=drivesdk

with 10.10 I get proxy timeouts non stop ( same proxies, same settings) just new capmonster version

 

[VladZen]

I have 50 threads, its been stable at ~ 1k per minute for months ( same settings)
Using chrome, desktop proxy, rotating residential ones
https://drive.google.com/file/d/1sBaP1vsO09M3FT3MoPMOlmwJPfVqQlU4/view?usp=drivesdk

with 10.10 I get proxy timeouts non stop ( same proxies, same settings) just new capmonster version

This is recaptcha2 and you should already know that it constantly changes. What worked yesterday, won't work today.
I'm sure you'll get the same result with 2.10.9.0 currently.

 

[Bringomatix]

those are results that I'm getting with 2.10.9
with the new one 2.10.10 I'm not getting not even close results. that's why I'm saying its bugged.
same proxies same settings, new capcha monster... = different results, way different

 

[Jernej]

I'm having the same issue. In addition to that I'm getting RCInstance crash errors and at some point Running tasks was up to 4000+

I'm downgrading 2.10.9 now.

Right after downgrade CapMonster went from 200 captchas/min (with timeouts and errors) back to 1100 captchas/min.

I didn't change any settings, sites or proxies, also tried updating modules but it didn't help.

However 2.10.9 is throwing waaaaaaay less RCInstance crash errors (one or two per day), compared to 2.10.10 which threw a bunch in just a few hours and caused whole server to freeze (HP Z820 with 2x Xeon E5-2667 v2, 128GB ECC ram, SSD).

I'm guessing timeouts and errors are result of high CPU load which is probably caused by RCInstance errors.

In event viewer I can still see old errors:

Faulting application name: RC2InstanceChrome.exe, version: 1.0.0.0, time stamp: 0x5cc19ee5
Faulting module name: libcef.dll, version: 3.3440.1805.0, time stamp: 0x5b6496ec
Exception code: 0xc0000005
Fault offset: 0x015df57b
Faulting process id: 0x4aa4
Faulting application start time: 0x01d5007acd2c19db
Faulting application path: C:\Program Files\ZennoLab\EN\CapMonster Pro\2.10.10.0\Progs\RC2InstanceChrome.exe
Faulting module path: C:\Program Files\ZennoLab\EN\CapMonster Pro\2.10.10.0\Progs\Chromium\libcef.dll
Report Id: 47802c70-6c6e-11e9-a717-40a8f0ca72ee

Application: RC2InstanceChrome.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 112BF57B
Stack:

those two repeating again and again always in pair.

Hope this helps.

 

[VladZen]

those are results that I'm getting with 2.10.9
with the new one 2.10.10 I'm not getting not even close results. that's why I'm saying its bugged.
same proxies same settings, new capcha monster... = different results, way different

I'm having the same issue. In addition to that I'm getting RCInstance crash errors and at some point Running tasks was up to 4000+

I'm downgrading 2.10.9 now.

Right after downgrade CapMonster went from 200 captchas/min (with timeouts and errors) back to 1100 captchas/min.

I didn't change any settings, sites or proxies, also tried updating modules but it didn't help.

However 2.10.9 is throwing waaaaaaay less RCInstance crash errors (one or two per day), compared to 2.10.10 which threw a bunch in just a few hours and caused whole server to freeze (HP Z820 with 2x Xeon E5-2667 v2, 128GB ECC ram, SSD).

I'm guessing timeouts and errors are result of high CPU load which is probably caused by RCInstance errors.

In event viewer I can still see old errors:

Faulting application name: RC2InstanceChrome.exe, version: 1.0.0.0, time stamp: 0x5cc19ee5
Faulting module name: libcef.dll, version: 3.3440.1805.0, time stamp: 0x5b6496ec
Exception code: 0xc0000005
Fault offset: 0x015df57b
Faulting process id: 0x4aa4
Faulting application start time: 0x01d5007acd2c19db
Faulting application path: C:\Program Files\ZennoLab\EN\CapMonster Pro\2.10.10.0\Progs\RC2InstanceChrome.exe
Faulting module path: C:\Program Files\ZennoLab\EN\CapMonster Pro\2.10.10.0\Progs\Chromium\libcef.dll
Report Id: 47802c70-6c6e-11e9-a717-40a8f0ca72ee

Application: RC2InstanceChrome.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 112BF57B
Stack:

those two repeating again and again always in pair.

Hope this helps.

Please delete all files from the folder Logs in CapMonster\Progs program directory.
Then enable extended log on program settings and reproduce the problem with timeout erros and instance crash.
After than run Diagnostic.exe from program directory not closing capmonster itself.
Send resulted report.zip to [email protected] with the link to problem description.

 

[naser gh]

hello , is there something wrong with chrome method ? my cap dont work and send “ proxy has been banned “
cap didnt work completely with other methods too

 

[VladZen]

hello , is there something wrong with chrome method ? my cap dont work and send “ proxy has been banned “
cap didnt work completely with other methods too

Please run module updating in program settings, as I asked above.

 

[naser]

Please run module updating in program settings, as I asked above.

its updated

 

[VladZen]

its updated

Then please make report as requested above.

 

[s00ny5]

Hello guys,

After new install for this version I got the proxy error ban thing to so I changed the proxies from list like this

From socks5://127.0.0.1:24000 to 127.0.0.1:24000
and selected socks5 in proxy settings.

http://prntscr.com/nm0k7m

all started to work again

 

[s00ny5]

I would also like to ask how we use the user@pass socks proxy now as like this:
user:[email protected]:23938

does not work.

regards

 

[VladZen]

socktype://user:[email protected]:23938
and yes, socks work bad with Chrome

 

[s00ny5]

socktype:// in front of proxy dont work on 10.10 any more

removed socktype:// and they started to work.

bad or no on chrome they always worked for 5 cm2 versions I used it.

 

[VladZen]

socktype:// in front of proxy dont work on 10.10 any more

removed socktype:// and they started to work.

bad or no on chrome they always worked for 5 cm2 versions I used it.

I meant sock5:// or socks4://, hope you got it.

 

[s00ny5]

.... is what I explained first

I was using socks5:// and when 10.10 started I got only bad proxy and banned. removed the socks5 part and started to work ..

 

[naser]

.... is what I explained first

I was using socks5:// and when 10.10 started I got only bad proxy and banned. removed the socks5 part and started to work ..

Can you guys please send picture of all tabs capmonster settings that i can change setting like you and make it work like you , i will be thankful

 

[s00ny5]

http://prntscr.com/nm0k7m

 

[naser]

http://prntscr.com/nm0k7m

All tabs please

 

[VladZen]

Can you guys please send picture of all tabs capmonster settings that i can change setting like you and make it work like you , i will be thankful

I asked you to send us diagnostic report)

 

[VladZen]

.... is what I explained first

I was using socks5:// and when 10.10 started I got only bad proxy and banned. removed the socks5 part and started to work ..

Not sure what is the problem in it... Now socks addresses work without typing socks:// at address. This is even more convenient.

 

[ravik]

Hi. I'm getting <no response> on rc2 chrome since 2hours... version 2.10.10, checked everything on my side. I restored the previous version and it didn't work also. On another machine everything works. PS: I see that only trafficlights giving good solutions but every other task <no response> ??