Gauge could not initialize, unable to get Debug Scenario option

[deepesh1511]

Description

I am unable to get Debug Scenario option on the spec files. This issue occurs in a specific scenario and I am able to reproduce the same multiple times.

Environment Details

Extensions

Debugger for Java v0.47.0
Extension Pack for Java v0.25.7
Gauge v0.1.0
Language Support for Java(TM) by Red Hat v1.13.0
Maven for Java v0.40.3
Project Manager for Java v0.21.1
Test Runner for Java v0.37.1

IDE

VS Code - v1.74.3

Steps to reproduce

Unsuccessful attempt --

• Open all background applications, and increase the CPU utilization.
• Open project in VS code
• VS code will try to load java project - project will be loaded successfully
• Vs code will try to load Gauge - gauge will not be initialized
  
• Debug Scenario option will not be displayed
  
• lsp.log
  

Successful attempt --

• Close all background applications, and reduce the CPU utilization.
• Open project in VS code
• VS code will try to load java project - project will be loaded successfully
• Vs code will try to load Gauge - gauge will be loaded successfully
• Wait for gauge to load and then open any spec file.
• Debug Scenario option will be displayed
  
• lsp.log
  current runner is not compatible with gauge LSP is not displayed in lsp.log
• Note: If I open any spec file during java project load, gauge will not initialize and Debug Scenario option will not be displayed. I need to wait for java project load to complete and additional one or two minutes before I can load a spec file to see debug option.

Expected Result

Debug Scenario should be displayed always, irrespective of CPU utilization.

Actual Result

Debug Scenario is not displayed always and project load depends on CPU utilization.

[deepesh1511]

@sriv @zabil Can you please take a look?

[deepesh1511]

I upgraded my VDI machine configuration (from 2 core to 4 cores) and then I was able to load the project successfully. Is there any minimum system requirement to run the gauge smoothly?

I also noted that Debug Scenario doesn't show up if the project is loaded with multiple different applications running in the background (Teams, outlook, chrome, edge) and occupying the CPU utilization.

[jensakejohansson]

I have noticed something very similar to this too, on a co-workers machine. Using Gauge/C# though, but the symptoms are the same. The Gauge project is rather big, yes, but the machine is not so "weak" so I find it a bit worring that it seems so easy to crash it. Will investigate further when I have time, but the extension seems to be unstable if the resources are limited...

[chadlwilson]

Make sure they have updated gauge and plugins along with the extension at the very least. Otherwise need to get the logs and all that, from both extension and gauge itself 😓

[jensakejohansson]

A comment for this old issue - if someone searches for help:

When I see this problem (even though I use dotnet not Java) it's seems be a timeout that occurs when loading larger projects in VSC. So if anyone has this issue, try to increase the configured Gauge timeouts. Specifically it seems to be the runner_connection_timeout. Check your timeouts and increase them and see if it makes a difference.

I have reasonable powerful laptop (i7-11850H @2.5GHz 8 Cores / 32GB memory), but it can take around 1 minute before Gauge has loaded my test project completely.

If/when I find the time I will attach debuggers to Gauge and see if I can find anything that can be improved in terms of performance.