Here test example:
The code is not prefect, but it's demonstrates the problem.
So, when I download more than 2 files simultaneous from one server (in my example I download 3 simultaneously) by InetGet() with background option, I will get only 2 active downloads. It's seems like server limitation. The third will remain with 0 read bytes until one of the previous downloads would finished. And if I want to close this third 0 bytes read download with InetClose() I will get hang of Window GUI for several seconds! After that, the third download would be closed and everything will continue to work normally.
If I InetClose() one of the active downloads with more than 0 bites read - all works fine!
You can try by your self given example, or watch this .gif's:
1. Window GUI hangs when I trying to Cancel (InetClose()) download with 0 bytes read download:
2. All works as it should, when I Cancel more than 0 bytes read download:
Any ideas why is it happens?
I was wondering if you can help me with the function called; InetRead().
My scripts are using this function a lot for several conditions and everything works fine!
But sometimes when the server is a little bit buggy of simply not available my script is hanging.
It takes about 90sec before this function returns a Timeout, when i adjust the parameter it still is hanging about 90sec.
The following script is a example where the script is hanging for aprox. 90sec;
; Set Timeout to 2sec AutoItSetOption ("TCPTimeout", 2000) ; Read Website InetRead("http://www.geenverbinding.nl/",1) ; Show Msgbox before Ending Script. Msgbox(64,"","Finished")
The following script is a example where the script show the Msgbox pretty fast;
; Set Timeout to 2sec AutoItSetOption ("TCPTimeout", 2000) ; Read Website InetRead("http://www.google.nl/",1) ; Show Msgbox before Ending Script. Msgbox(64,"","Finished")
My question now is, what am i doing wrong and/or is there a other way to prevent Hanging the script?
any suggestion to track down, why a script is freezing after a longer run time?
This is a general question, I've checked the common mistakes, I've made so far (inside a loop doing fileopen() without fileclose(), runwait() for progs, that don't terminate, infinite recursive loops etc.)
This script stops just after several days of running...
Is there a direct way to "count" the amount of MEM and handles, a autoit script is using itself, or by child processes?
I recently installed AutoIT(the most recent version) on my work computer and everytime I try to use Koda to generate code for a GUI Koda freezes....nothing can be clicked on and I have to use task manager to end the task. It doesn't seem to matter if I open a file or if I try with a fresh design. It also freezes if I try to change any settings within Koda
I've tried uninstalling everything AutoIT related and reinstalling and restarting the computer. No matter what it still does it
Is there a setting somewhere that could be causing this?