Debug Log

To check whether the Sigasi extension started successfully, you should navigate to Sigasi’s output view. This can be done through the Command Palette (Ctrl+Shift+P) and select Sigasi: Open Log.

The Output View should say Language client connected from ...

The logs in the Sigasi output view contain possible errors from client and server. If errors are present, you are advised to copy them and include them in your email to support+vscode@sigasi.com.

SLF4J Errors

The following error messages in the Output View can be safely ignored.

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.

OutOfMemoryError: Java Heap Space

If Java runs out of memory, you will see a java.lang.OutOfMemoryError: Java heap space in the log.

To avoid this, go to the settings (Ctrl+Shift+P > Preferences: Open Settings (UI) > Sigasi). Here you can set the Sigasi > Server: Arguments. Increase the value for Xmx to more than the default 3g.

The heap space setting is identical to the one used in Sigasi Studio.


Server Logs

On some occasions we might ask you to share the server logs.

Before obtaining the server logs it’s best to enable debug logging. For more detailed logging, open the settings and change Sigasi > Server > Log: Level to debug.

The location of the server logs depends on your OS.

  • On Linux, the logs are below ~/.config/Code/logs
  • On Windows, the logs are in %AppData%\Code\logs

Then find [datetime]/window[1]/exthost/output_logging_[datetime]/[0-9]-Sigasi{Tracing}.log. For each occurrence of [datetime], choose the most recent directory available.

We recommend to open the exthost folder using the command Developer: Open Extension Logs Folder.

Note: These logs contain file names from your project so only send them to us if you’re allowed to do so.