At least, Disconnect() can help to close websocket connections (to pages) which are not needed anymore. Otherwise, you can run out of them pretty quick (as the default is 6, afaik, which can be changed only by registry edit) if you try to handle many different tabs, eventually resulting in a 'security error' message. This means, this might happen long before any ExitApp might be called.neogna2 wrote: ↑16 Jun 2021, 07:47About PageInst.Disconnect() the Chrome.ahk source saysBut isn't the memory released when the script exits with ExitApp anyway, making Disconnect() redundant there?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.
Not sure, if there are other implications... but the quote seems to hint at possible memory issues at well, also connected to the websocket connection(s). It surely doesn*t hurt to disconnect, when you are done with a page - at least, if you are not planning to close the script soon.