Sonarlint VS code not showing errors after save

Please provide

  • Operating system: RHEL 8
  • IDE name and flavor/env: VS code 1.66.2
  • SonarLint plugin version: 3.4.1
  • Is connected mode used:
    • Connected to SonarCloud or SonarQube (and which version):

And a thorough description of the problem / question:
Sonarlint errors appear on file on opening of visual studio. After saving the file, not having fixed the errors, the errors are no longer appearing in the file. Closing and reopening the file shows 0 errors. Closing and reopening visual studio code shows the errors again

Hello @Padraig,

Could you share with us the debug logs so we can help you ?

Thanks

Found this error in the logs

Error - 16:10:31.717] 
[Error - 16:10:31.717] <--- Last few GCs --->
[Error - 16:10:31.717] 
[Error - 16:10:31.717] [102886:0x664bdc0]   132539 ms: Mark-sweep 9859.0 (10033.3) -> 9853.6 (10045.8) MB, 2569.5 / 0.0 ms  (average mu = 0.854, current mu = 0.473) allocation failure scavenge might not succeed
[Error - 16:10:31.717] [102886:0x664bdc0]   138412 ms: Mark-sweep 9869.9 (10046.3) -> 9865.5 (10058.8) MB, 5798.6 / 0.0 ms  (average mu = 0.559, current mu = 0.013) allocation failure scavenge might not succeed
[Error - 16:10:31.717] 
[Error - 16:10:31.717] 
[Error - 16:10:31.717] <--- JS stacktrace --->
[Error - 16:10:31.717] 
[Error - 16:10:31.717] FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
[Error - 16:10:31.719]  1: 0xb09980 node::Abort() [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.719]  2: 0xa1c235 node::FatalError(char const*, char const*) [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.719]  3: 0xcf784e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.720]  4: 0xcf7bc7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.720]  5: 0xeaf465  [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.721]  6: 0xebf12d v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.721]  7: 0xec1e2e v8::internal::Heap::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.722]  8: 0xe8336a v8::internal::Factory::NewFillerObject(int, bool, v8::internal::AllocationType, v8::internal::AllocationOrigin) [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.722]  9: 0x11fc0b6 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Error - 16:10:31.723] 10: 0x15f0b19  [/home/pmweeks/.nvm/versions/node/v16.14.2/bin/node]
[Info  - 16:10:35.856] 0/1 files analyzed, current file: /<file>/<file>
[Error - 16:10:38.127] eslint-bridge Node.js process is unresponsive. This is most likely caused by process running out of memory. Consider setting sonar.javascript.node.maxspace to higher value (e.g. 4096).
[Error - 16:10:38.129] Failure during analysis, Node.js command to start eslint-bridge was: /home/pmweeks/.nvm/versions/node/v16.14.2/bin/node /home/pmweeks/.sonarlint/work/.sonartmp_1394246500511299117/eslint-bridge-bundle/package/bin/server 43529 127.0.0.1 /<file> true true 
[Error - 16:10:38.131] java.lang.IllegalStateException: eslint-bridge is unresponsive
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.request(EslintBridgeServerImpl.java:270)
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.analyzeTypeScript(EslintBridgeServerImpl.java:239)
	at org.sonar.plugins.javascript.eslint.TypeScriptSensor.analyze(TypeScriptSensor.java:151)
	at org.sonar.plugins.javascript.eslint.TypeScriptSensor.analyzeFilesWithTsConfig(TypeScriptSensor.java:138)
	at org.sonar.plugins.javascript.eslint.TypeScriptSensor.analyzeFiles(TypeScriptSensor.java:114)
	at org.sonar.plugins.javascript.eslint.AbstractEslintSensor.execute(AbstractEslintSensor.java:67)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.sensor.SensorsExecutor.executeSensor(SensorsExecutor.java:81)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.sensor.SensorsExecutor.execute(SensorsExecutor.java:72)
	at org.sonarsource.sonarlint.core.analysis.container.analysis.AnalysisContainer.doAfterStart(AnalysisContainer.java:122)
	at org.sonarsource.sonarlint.core.plugin.commons.pico.ComponentContainer.startComponents(ComponentContainer.java:119)
	at org.sonarsource.sonarlint.core.plugin.commons.pico.ComponentContainer.execute(ComponentContainer.java:104)
	at org.sonarsource.sonarlint.core.analysis.container.module.ModuleContainer.analyze(ModuleContainer.java:71)
	at org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand.execute(AnalyzeCommand.java:58)
	at org.sonarsource.sonarlint.core.analysis.command.AnalyzeCommand.execute(AnalyzeCommand.java:32)
	at org.sonarsource.sonarlint.core.analysis.AnalysisEngine$AsyncCommand.execute(AnalysisEngine.java:152)
	at org.sonarsource.sonarlint.core.analysis.AnalysisEngine.executeQueuedCommands(AnalysisEngine.java:70)
	at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.io.IOException: HTTP/1.1 header parser received no bytes
	at java.net.http/jdk.internal.net.http.HttpClientImpl.send(HttpClientImpl.java:565)
	at java.net.http/jdk.internal.net.http.HttpClientFacade.send(HttpClientFacade.java:119)
	at org.sonar.plugins.javascript.eslint.EslintBridgeServerImpl.request(EslintBridgeServerImpl.java:262)
	... 16 more
Caused by: java.io.IOException: HTTP/1.1 header parser received no bytes
	at java.net.http/jdk.internal.net.http.common.Utils.wrapWithExtraDetail(Utils.java:327)
	at java.net.http/jdk.internal.net.http.Http1Response$HeadersReader.onReadError(Http1Response.java:673)
	at java.net.http/jdk.internal.net.http.Http1AsyncReceiver.checkForErrors(Http1AsyncReceiver.java:297)
	at java.net.http/jdk.internal.net.http.Http1AsyncReceiver.flush(Http1AsyncReceiver.java:263)
	at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SynchronizedRestartableTask.run(SequentialScheduler.java:175)
	at java.net.http/jdk.internal.net.http.common.SequentialScheduler$CompleteRestartableTask.run(SequentialScheduler.java:147)
	at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:198)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
	... 1 more
Caused by: java.io.EOFException: EOF reached while reading
	at java.net.http/jdk.internal.net.http.Http1AsyncReceiver$Http1TubeSubscriber.onComplete(Http1AsyncReceiver.java:591)
	at java.net.http/jdk.internal.net.http.SocketTube$InternalReadPublisher$ReadSubscription.signalCompletion(SocketTube.java:632)
	at java.net.http/jdk.internal.net.http.SocketTube$InternalReadPublisher$InternalReadSubscription.read(SocketTube.java:833)
	at java.net.http/jdk.internal.net.http.SocketTube$SocketFlowTask.run(SocketTube.java:175)
	at java.net.http/jdk.internal.net.http.common.SequentialScheduler$SchedulableTask.run(SequentialScheduler.java:198)
	at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:271)
	at java.net.http/jdk.internal.net.http.common.SequentialScheduler.runOrSchedule(SequentialScheduler.java:224)
	at java.net.http/jdk.internal.net.http.SocketTube$InternalReadPublisher$InternalReadSubscription.signalReadable(SocketTube.java:763)
	at java.net.http/jdk.internal.net.http.SocketTube$InternalReadPublisher$ReadEvent.signalEvent(SocketTube.java:941)
	at java.net.http/jdk.internal.net.http.SocketTube$SocketFlowEvent.handle(SocketTube.java:245)
	at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.handleEvent(HttpClientImpl.java:957)
	at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.lambda$run$3(HttpClientImpl.java:912)
	at java.base/java.util.ArrayList.forEach(ArrayList.java:1541)
	at java.net.http/jdk.internal.net.http.HttpClientImpl$SelectorManager.run(HttpClientImpl.java:912)

Increased node heap size and got around error
Think error message should be updated to indicate there was an error instead of just displaying no errors

As suggested in the error message it could be a memory usage problem.

You can find here how to set this property for your project.

Could you confirm if this helped fix the issue ?

Oh thanks for the update, glad it worked.

Indeed yes, this error should be made more visible. I created a ticket to improve that.

Thanks for reporting!