microsoft / microsoft/vscode-java-pack
Failed to update qualified index
Open
Nobody has claimed this yet.
ai-triaged
bug
- Dominant language
- TypeScript
- Stars
- 352
- Forks
- 166
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 32
Description
!ENTRY org.eclipse.jdt.core 4 0 2022-11-08 09:16:17.551
!MESSAGE Failed to update qualified index.
!STACK 0
java.io.IOException: Failed to read index data from file:/C:/Users/admin/AppData/Roaming/Code/User/workspaceStorage/c6f99d609a500868211607affa7d771b/redhat.java/jdt_ws/.metadata/.plugins/org.eclipse.jdt.core/1865797976.index at offset 1174 and size 808923700
at org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable(DiskIndex.java:685)
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.index.MetaIndex.save(MetaIndex.java:100)
at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveMetaIndex(IndexManager.java:1256)
at org.eclipse.jdt.internal.core.search.indexing.IndexManager.saveIndexes(IndexManager.java:1232)
at org.eclipse.jdt.internal.core.search.indexing.IndexManager.notifyIdle(IndexManager.java:826)
at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:458)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.OutOfMemoryError: Java heap space
at org.eclipse.jdt.internal.compiler.util.HashtableOfObject.<init>(HashtableOfObject.java:56)
at org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable(DiskIndex.java:681)
... 10 more
Contributor guide
No contributing guide indexed for this repository
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
Start with the reported failure in org.eclipse.jdt.internal.core.index.DiskIndex.readCategoryTable at DiskIndex.java:681 and trace how IndexManager.saveIndexes reaches it. Reproduce the Java heap exhaustion if possible, then establish a concrete fix or mitigation that prevents the qualified index update from failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100