microsoft / microsoft/azure-tools-for-java
[IntelliJ] Uncaught Exception com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file:///Users/a38411/Documents/taxation-omsmerge/oms-purchase/pom.xml; original:450753; found:452197; File.exists()=true
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 262
- Forks
- 185
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 1
Description
IntelliJ build version: 2025.1.3 IC-251.26927.53
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.7
Plugin version: 3.95.0-2025.1
Additional Info: None
Parent component:
com.intellij.openapi.wm.impl.IdeRootPane[,0,0,1728x1080,layout=com.intellij.openapi.wm.impl.IdeRootPane$CustomHeaderRootLayout,alignmentX=0.0,alignmentY=0.0,border=,flags=449,maximumSize=,minimumSize=,preferredSize=]
Error message:
IdeaLoggingEvent[message=null, throwable=com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: <REDACTED: user-file-path>; original:450753; found:452197; File.exists()=true
at com.intellij.psi.impl.file.impl.FileManagerImpl.findFile(FileManagerImpl.java:507)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.lambda$checkDependencyManagement$7(MavenProjectReportGenerator.java:269)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.checkDependencyManagement(MavenProjectReportGenerator.java:269)
at com.microsoft.azure.toolkit.intellij.java.sdk.MavenProjectReportGenerator.analyzePom(MavenProjectReportGenerator.java:158)
at com.micr
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The stack trace points to MavenProjectReportGenerator.java, especially checkDependencyManagement at line 269 and analyzePom at line 158; start by tracing the call to FileManagerImpl.findFile. Reproduce the IntelliJ Maven analysis scenario if possible and determine how the invalid virtual file is reached. Done means the reported uncaught exception no longer occurs in that path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100