Debug version
Debug version is useful if you want to report about application crush, browser crush or memory leak. It is not recommended to use debug version for everyday development because it runs slower and doesn't support script compilation.
How to report about BAS crush?
BAS crush means that whole application gets suddenly closed.
In order to test it, execute ScriptWorker.DebugTerminate(1);
- Download debug version, links available below.
- Run BrowserAutomationStudio.exe.
- Reproduce crush.
- After crush, crashdump_bas.dmp file will appear in the same folder as BrowserAutomationStudio.exe. Send this file to mail.to.twaego@gmail.com
How to report browser crush?
When browser crushes, only browser window gets closed, main application remains to work.
In order to test it, execute _simulate_crush()!
- Download debug version, links available below.
- Rename Worker folder into WorkerRelease.
- Rename WorkerDebug folder into Worker.
- Run BrowserAutomationStudio.exe.
- Reproduce crush.
- After crush, crashdump_chrome.dmp file will appear in the same folder as BrowserAutomationStudio.exe. Send this file to mail.to.twaego@gmail.com.
Debug version may be unstable and can crush even when release version will work fine. Please ensure, that bug reproduces on release version also before sending dump.
How to report about memory leak
Memory leak means that amount of memory allocated by BrowserAutomationStudio.exe process constantly gets growing.
- Download debug version, links available below.
- Run SetFlags.bat
- Run BrowserAutomationStudio.exe.
- Run the script, get to the point where memory begins to flow.
- Run TraceMemoryStart.bat, this batch is located in same folder as BrowserAutomationStudio.exe.
- Take the necessary actions so that the memory leaks.
- Run TraceMemoryEnd.bat.
- A.txt and B.txt files will appear in the same folder as BrowserAutomationStudio.exe. Send this file to mail.to.twaego@gmail.com.
