Failed to save JDT index

[Eskibear]

Different call stacks below:

java.io.UTFDataFormatException
	at org.eclipse.jdt.internal.core.index.DiskIndex.readStreamChars(DiskIndex.java:983)
	at org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable(DiskIndex.java:689)
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategory(DiskIndex.java:485)
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeCategories(DiskIndex.java:477)
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(DiskIndex.java:579)
	at org.eclipse.jdt.internal.core.index.Index.save(Index.java:230)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(IndexManager.java:1143)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndexes(IndexManager.java:1201)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.notifyIdle(IndexManager.java:819)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:422)

java.io.FileNotFoundException: xxxxxxx yyyyyyy (No such file or directory)
	at (Native Method)
	at (Unknown Source)
	at <init>(Unknown Source)
	at org.eclipse.jdt.internal.core.index.FileIndexLocation.getInputStream(FileIndexLocation.java:81)
	at org.eclipse.jdt.internal.core.index.DiskIndex.readAllDocumentNames(DiskIndex.java:630)
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(DiskIndex.java:532)
	at org.eclipse.jdt.internal.core.index.Index.save(Index.java:230)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(IndexManager.java:1143)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndexes(IndexManager.java:1201)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.notifyIdle(IndexManager.java:819)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:422)

java.io.IOException: Stream was closed for index location "xxxxxxx"
	at org.eclipse.jdt.internal.core.index.DiskIndex.readChunk(DiskIndex.java:751)
	at org.eclipse.jdt.internal.core.index.DiskIndex.readAllDocumentNames(DiskIndex.java:640)
	at org.eclipse.jdt.internal.core.index.DiskIndex.mergeWith(DiskIndex.java:532)
	at org.eclipse.jdt.internal.core.index.Index.save(Index.java:230)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndex(IndexManager.java:1143)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndexes(IndexManager.java:1201)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.notifyIdle(IndexManager.java:819)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:422)

[rgrunber]

Looks similar to redhat-developer/vscode-java#2232 , except that also shows an OOM occurring.

[github-actions]

Hi @Eskibear, 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.

Suggested Workarounds

• Corrupted index files often cause these JVM errors. Close your IDE, then delete all index data under your workspace:

  {workspace}/.metadata/.plugins/org.eclipse.jdt.core/*.index*
  

  Restart the IDE; JDT will rebuild those indexes automatically.

• Make sure no external process (e.g. antivirus, backup tools) is holding locks on the index files when the IDE is idle.

• If you’re on VS Code with jdt.ls, run “Java: Clean the Java language server workspace” from the command palette to purge and regenerate caches.

Related Issue (high confidence)

• After a class is repeated multiple times, dd re-enters, and then dd deletes, and there will be no prompt (#3270): same DiskIndex call stack leading to a corrupted index. Users reported deleting the index files resolved the error.
  After a class is repeated multiple times, dd re-enters, and then dd deletes, and there will be no prompt eclipse-jdtls/eclipse.jdt.ls#3270

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!

[Eskibear]

closing this as stale