Seeing: Cannot read field "path" because "lspframe.source" is null in cursor #1591

Activity

1. github-actions commented on Dec 4, 2025

   

   github-actionsBot

   on Dec 4, 2025 – with GitHub Actions

   More actions

   Hi iamwasoomro786-creator, I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

   Suggestions

   • Update to the latest Java Debugger and Java Extension Pack (avoid custom openvsix builds): install from the VS Code Marketplace to ensure all dependencies match.
   • Clean and restart the Java Language Server: run Java: Clean Java Language Server Workspace and reload the window.
   • Enable verbose logging and capture output:
     • In settings.json set:

       {
         "java.trace.server": "verbose",
         "java.trace.debug": "verbose"
       }

     • Reproduce the error and attach the logs when filing a bug.
   • Use a proper Java launch config (e.g. Launch Java), not an npm-based launch, to ensure the Java Debug Adapter populates lspFrame.source correctly.

   References

   • Java help (Fix the duplicated error dialog after the user clicks Learn More #380): users saw similar path argument errors resolved by upgrading to the latest Java Extension Pack.
     Java help vscode-java-pack#380
   • Get NPE when opening a non-java file (Update changelog for 0.3.0 #139): an NPE reading path due to null source was reported when an unsupported file type was opened.
     Get NPE when opening a non-java file vscode-java-dependency#139

   No duplicates found.

   The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
2. github-actions

   added

   ai-triaged

   bug

   on Dec 4, 2025
3. iamwasoomro786-creator commented on Dec 4, 2025

   

   iamwasoomro786-creator

   on Dec 4, 2025

   Author

   More actions

   Again in debugger

   

   And have attached the logs here

   java_debugger_logs.log
4. iamwasoomro786-creator

   closed this as completedon Dec 4, 2025