
There is another parameter -disable-crash-reporter which is said to override that behaviour. Remote Access: Uses network protocols on unusual ports Spyware: POSTs files to.

Crashpad is a crash-reporting system and it seems using -headless enables crash reporting by default and makes Chrome upload crash data to Google's servers. This report is generated from a file or URL submitted to this webservice. At one time I noticed a second chrome.exe process which was running with the parameter -type=crashpad-handler. Doesn't happen when no process name filtering is applied.ģ. If the Microsoft tool Process Explorer is running and filtered to processes with name "chrome.exe" then starting a Chrome.ahk script causes Process Explorer to close. event - the Log window itself did not appear in the log - File Folders. I have when testing stuff seen a few cases where a chrome.exe process lingers after the AutoHotkey script exits which I think (not sure though) was caused by trying to run multiple Chrome.ahk scripts at the same time and it happened both with headless and non-headless mode.Ģ. Window Actions, Title Buttons: The Align Window title button did not restore.

This method should always be called when you are finished with a page or else your script will leak memory.īut isn't the memory released when the script exits with ExitApp anyway, making Disconnect() redundant there?ġ. Hybrid Analysis develops and licenses analysis tools to fight malware.

Objectdock plus crash report file can not open for free#
Disconnect from the page's debug interface, allowing the instance to be garbage collected. Submit malware for free analysis with Falcon Sandbox and Hybrid Analysis technology.
