How to use error handling to deal with Websocket Error

[songdg]

While using Chrome.ahk to do repeated stuff.

[gregster]

That's a pretty unspecific question. But generally, the default maximum for websocket connections (at least the way it is done by Chrome.ahk) is 6. If you exceed it, you'll probably get some kind of "security error". Afaik, this limit can be raised by changing the registry (at your own risk).

But generally it is more important to use Chrome.ahk's Disconnect() method on tabs that you are done with. From the Chrome.ahk source code:

Code: Select all

	/*
			Disconnect from the page's debug interface, allowing the instance
			to be garbage collected.
			
			This method should always be called when you are finished with a
			page or else your script will leak memory.
		*/
		Disconnect()
		{  ; [...]

If your question is about something else, please elaborate!

[songdg]

That's a pretty unspecific question. But generally, the default maximum for websocket connections (at least the way it is done by Chrome.ahk) is 6. If you exceed it, you'll probably get some kind of "security error". Afaik, this limit can be raised by changing the registry (at your own risk).

But generally it is more important to use Chrome.ahk's Disconnect() method on tabs that you are done with. From the Chrome.ahk source code:

Code: Select all

	/*
			Disconnect from the page's debug interface, allowing the instance
			to be garbage collected.
			
			This method should always be called when you are finished with a
			page or else your script will leak memory.
		*/
		Disconnect()
		{  ; [...]

If your question is about something else, please elaborate!

Thanks, I had been used the Disconnect() function already, but the problem persists.Here is the main structure of my code in a loop.

Code: Select all

open a new tab(used the Findtext library)
GetPage()
do something...
Call("Page.close")
Disconnect()

[gregster]

There is still no problem description - for me, this is too unspecific to make another guess.

But if you are only looking generally for some error handling, try and catch might help.

If your question is about something else, please elaborate!

[songdg]

There is still no problem description - for me, this is too unspecific to make another guess.

But if you are only looking generally for some error handling, try and catch might help.

If your question is about something else, please elaborate!

Now I just comment out the "Websocket Error!" exception in the Chrome.ahk library, and it seems there is no side effects so far.