Skip to content

3. Backend Devtools

Jump to bottom
Peter van der Walt edited this page May 6, 2020 · 5 revisions

Debugging OpenBuildsCONTROL

OpenBuildsCONTROL runs on a nodejs/electronjs backend. The following document outlines how to use the --inspect switch to connect Chrome Devtools to the "server" side of CONTROL (the backend) to access debug information:

  1. Install latest NodeJS: https://nodejs.org/en/download/

  2. Quit the running instance of OpenBuildsCONTROL from the system tray menu

enter image description here

  1. Find the OpenBuildsCONTROL shortcut you use to start it with, and edit the shortcut. Find the Target and append "--inspect" to the end:

enter image description here

  1. Run the application using this shortcut.
  2. Open an instance of Google Chrome and press Ctrl+Shift+i to open Chrome Devtools
  3. You'll notice a Node button in the Devtools window:

enter image description here

  1. Click this button to launch a Devtools instance connected to the OpenBuildsCONTROL backend process:

enter image description here

  1. Use the performance/profiler tab to gather a process profile, and the memory tab to grab a to gather stack, etc to debug the backend. Save them to disk and attach to bug reports
Clone this wiki locally