Troubleshooting Streamline crashes during a capture

If you run a capture session but Streamline crashes, you can locate the Java Virtual Machine (JVM) crash report and seek help from the Arm Support team.

Cause

The are various reasons which could cause Streamline to crash and exit during a capture session. Arm Support can help you to diagnose the cause and identify a solution.

Solution

Locate your JVM crash report file and contact Arm:

By default, the file name for JVM crash reports is hs_err_pid<pid>.log and is created in the working directory, unless:

  • You have manually set a different crash log location using the -XX:ErrorFile=<file> JVM argument.

    Note

    You can check or edit the value for this argument in the file that is appropriate for your OS and usage, either GUI or command line:

    • On Windows - in ./Streamline-gui.ini (GUI) or in ./Streamline-cli.in (command line)

    • On Linux - in /.Streamline-gui.ini (GUI) or in ./.Streamline-cli.ini (command line)

    • On MacOS - in "./Streamline.app/Contents/Eclipse/Streamline-gui.ini (GUI) or in ./Streamline.app/Contents/Eclipse/Streamline-cli.ini (command line)

    You can also set the value through the command line, for example, using streamline-gui -vmargs -XX:Errorfile=<file>.

  • Your working directory cannot be written to. Instead, you can find your crash reports at the default location for your OS:

    • On Linux - in tmp

    • On MacOS - in tmp

    • On Windows - in the location set by the TMP or TEMP environment variables. The default location is: C:Users<username>AppDataLocalTemp

If you still need help with your capture, send the gator-log.txt file, along with your capture, to the support team. The log file is in the same directory as the capture, and is available after the capture has finished. It records basic debugging and support information, such as errors, warnings, and information about the device.

To create a gator-log.txt file for a local capture, enable the --capture-log command line option.