Repository navigation
Java IntelliSense stops working randomly #1040
Description
Issue Type: Bug
I have been using a very small project for a few months now, and have had the best experience with the Java Language support. Intellisense was working great until the last 2 patches of Visual Studio Code, which apparently broke the extension. It throws an exception, and then all IntelliSense stops working, including the JS/TS extension. If I restart Visual Studio Code, it will start working again, until it hits the exception again. Here are the details:
[Error - 2:12:06 PM] Aug 21, 2019 2:12:06 PM Problem with folding range for /dev-charlie-plugin/src/progressive/pims/AccessRequestResource.java
Invalid_Char_In_String
org.eclipse.jdt.core.compiler.InvalidInputException: Invalid_Char_In_String
at org.eclipse.jdt.internal.core.util.PublicScanner.getNextToken(PublicScanner.java:1470)
at org.eclipse.jdt.ls.core.internal.handlers.FoldingRangeHandler.computeFoldingRanges(FoldingRangeHandler.java:110)
at org.eclipse.jdt.ls.core.internal.handlers.FoldingRangeHandler.foldingRange(FoldingRangeHandler.java:61)
at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$25(JDTLanguageServer.java:781)
at org.eclipse.jdt.ls.core.internal.handlers.JDTLanguageServer.lambda$42(JDTLanguageServer.java:915)
at java.util.concurrent.CompletableFuture.uniApply(CompletableFuture.java:602)
at java.util.concurrent.CompletableFuture$UniApply.tryFire(CompletableFuture.java:577)
at java.util.concurrent.CompletableFuture$Completion.exec(CompletableFuture.java:443)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1056)
at java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:1692)
at java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:157)
Extension version: 0.47.0
VS Code version: Code 1.37.1 (f06011ac164ae4dc8e753a3fe7f9549844d15e35, 2019-08-15T16:17:55.855Z)
OS version: Windows_NT x64 10.0.17763
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz (8 x 1896) |
| GPU Status | 2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: disabled_software oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_deferred_display_list: disabled_off skia_renderer: disabled_off surface_synchronization: enabled_on video_decode: enabled viz_display_compositor: disabled_off webgl: enabled webgl2: enabled |
| Load (avg) | undefined |
| Memory (System) | 15.85GB (7.08GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Activity
max-cool commentedon Aug 22, 2019
I stopped by to say that I'm having a similar issue. Intellisense will randomly stop after using VS Code for some time; it seems to break when loading certain method suggestions after typing a dot. After that, Intellisense stops completely.
I get the following javascript errors in the console when this happens (not sure how to see the java exceptions @ccerghed reports however).
I am running Windows 10 and VS Code 1.37.1 as well.
max-cool commentedon Aug 22, 2019
As an update, I can consistently trigger the Javascript errors when typing "System."
max-cool commentedon Aug 28, 2019
Is anyone looking at this? I may have to use a different tool as intellisense breaking frequently is disruptive
fbricon commentedon Aug 28, 2019
@maxi-billion can you provide the message output after turning on verbose tracing?
max-cool commentedon Aug 28, 2019
The javascript errors don't appear to be any different after enabling verbose tracing. The server log file also doesn't appear to report anything scary, but here it is anyways. This is in the timeframe of typing "System." to trigger the issue
snjeza commentedon Aug 28, 2019
@maxi-billion Could you disable the Spring Tools and Visual Studio IntelliCode extension and try to reproduce the issue?
max-cool commentedon Aug 28, 2019
@snjeza You nailed it! With Visual Studio IntelliCode disabled, the plugin does not fail anymore.
From searching IntelliCode in the issues here, it would seem this is a known issue, so I apologize.
ccerghed commentedon Aug 31, 2019
Thank you, I disabled IntelliCode and it fixed the issue for me as well.