[IntelliJ] Uncaught Exception com.intellij.openapi.vfs.InvalidVirtualFileAccessException: Accessing invalid virtual file: file:///Users/jatinupadhyaya/Documents/Workspace/CAT/customer-allocation-pool/spec/pom.xml; original:2514; found:141819; File.exists(

IntelliJ build version: 2025.2.1 IU-252.25557.131
OS: Mac OS X
JDK: JetBrains s.r.o. 21.0.8
Plugin version: 3.95.0-2025.2
Additional Info: None
Parent component:

com.intellij.openapi.wm.impl.IdeRootPane[,0,0,1728x1018,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:2514; found:141819; File.exists()=true
	at com.intellij.psi.impl.file.impl.FileManagerImpl.findFile(FileManagerImpl.java:515)
	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

Start with MavenProjectReportGenerator.checkDependencyManagement at line 269 and its call from analyzePom at line 158, then inspect the FileManagerImpl.findFile stack-frame context. Reproduce the reported IntelliJ 2025.2.1 failure against the referenced spec/pom.xml and determine the conditions for the invalid virtual file access. Done means the exception no longer occurs in this dependency-management analysis path.