-
Notifications
You must be signed in to change notification settings - Fork 100
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unfx Proxy Checker v1.6.1 got bug like old version , still blank white #31
Comments
Tested on the file have 44969 proxies , file size is 892kb , with Unfx Proxy Checker v1.5.2 and Unfx Proxy Checker v1.5.3 i can check a file biger than up to 4-5mb , it work fine. |
retest again with 21023 proxies it still blank but with 10000 it run fine , i think problem on limit list or rebuild the list of result |
@rchunter80 How much memory you have? I check ~90k always is ok. |
Tks my cpu using is xeon e5 2696 v3 with 64gb ram, i am running Unfx Proxy Checker on a vm , it have 13.9 gb ram , 16 core cpu . I think this can work good , so with old version checker can work good without problem but the older more ( sorry i don't remember correct version ) it have same problem , i just remember on version 1 is ok , next version have this error , next version is 1.5.2 and 1.5.3 is run good without error , and latest version this error come back |
hi , any news assnctr bro ? I hope u will fix this bug soon . Thanks for ur work hard |
Hi bro , can u edit update method just use alert only and we can update install it manual ? this can help me reuse old version without auto update , bsc look like old version can work good for me here and when i try reinstall it will update auto to latest version i can't do anything to stop this process . Thanks bro and hope u will fix this issue as soon as |
Hi , sorry after i have update unfx proxy checker to latest version is 1.6.1 it got bug like before from old version , click check and it just show blank , nothing can do continues , pls recheck i think u reuse old module on this .
The text was updated successfully, but these errors were encountered: