Bug 546625 - [new index] An internal error occurred during: "Restoring type hierarchy of 'Collection<E
Summary: [new index] An internal error occurred during: "Restoring type hierarchy of '...
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 4.11   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2019-04-22 06:31 EDT by Peter Bursch CLA
Modified: 2023-04-09 05:21 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Bursch CLA 2019-04-22 06:31:56 EDT
Pressing F4 on java.util.Collection yields

An internal error occurred during: "Restoring type hierarchy of 'Collection<E> - java.util'...".
Method close()V and method close()V both claim to be at position 9
Related addresses:
field 8, a FieldInt in struct NdMethod [address 460181906, size 4]: No modification report
field 8, a FieldInt in struct NdMethod [address 456488394, size 4]: No modification report
Comment 1 Andrey Loskutov CLA 2019-04-22 08:59:24 EDT
Please attach full error log and provide minimal steps to reproduce. Which JDK version and vendor was used? Can it be you are using "new" JDT index?
Comment 2 Peter Bursch CLA 2019-04-22 17:53:08 EDT
Yes, "new" index is used.
Stacktrace:

org.eclipse.jdt.internal.core.nd.db.IndexException: Method close()V and method close()V both claim to be at position 9
Related addresses:
field 8, a FieldInt in struct NdMethod [address 460181906, size 4]: No modification report
field 8, a FieldInt in struct NdMethod [address 456488394, size 4]: No modification report
	at org.eclipse.jdt.internal.core.nd.IndexExceptionBuilder.build(IndexExceptionBuilder.java:77)
	at org.eclipse.jdt.internal.core.nd.java.NdType.getMethodsInDeclarationOrder(NdType.java:270)
	at org.eclipse.jdt.internal.core.nd.java.model.IndexBinaryType.getMethods(IndexBinaryType.java:268)
	at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.cachePartsFrom(BinaryTypeBinding.java:550)
	at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:1041)
	at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.createBinaryTypeFrom(LookupEnvironment.java:1022)
	at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.accept(HierarchyResolver.java:122)
	at org.eclipse.jdt.internal.compiler.lookup.LookupEnvironment.askForType(LookupEnvironment.java:249)
	at org.eclipse.jdt.internal.compiler.lookup.UnresolvedReferenceBinding.resolve(UnresolvedReferenceBinding.java:114)
	at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.resolveType(BinaryTypeBinding.java:231)
	at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.superInterfaces(BinaryTypeBinding.java:2052)
	at org.eclipse.jdt.internal.compiler.lookup.BinaryTypeBinding.superclass(BinaryTypeBinding.java:2031)
	at org.eclipse.jdt.internal.core.hierarchy.HierarchyResolver.resolve(HierarchyResolver.java:833)
	at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.buildForProject(IndexBasedHierarchyBuilder.java:264)
	at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.buildFromPotentialSubtypes(IndexBasedHierarchyBuilder.java:349)
	at org.eclipse.jdt.internal.core.hierarchy.IndexBasedHierarchyBuilder.build(IndexBasedHierarchyBuilder.java:165)
	at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.compute(TypeHierarchy.java:323)
	at org.eclipse.jdt.internal.core.hierarchy.TypeHierarchy.refresh(TypeHierarchy.java:1319)
	at org.eclipse.jdt.internal.core.CreateTypeHierarchyOperation.executeOperation(CreateTypeHierarchyOperation.java:94)
	at org.eclipse.jdt.internal.core.JavaModelOperation.run(JavaModelOperation.java:736)
	at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:802)
	at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:898)
	at org.eclipse.jdt.internal.core.BinaryType.newTypeHierarchy(BinaryType.java:857)
	at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.createTypeHierarchy(TypeHierarchyLifeCycle.java:304)
	at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefresh(TypeHierarchyLifeCycle.java:335)
	at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle.doHierarchyRefreshBackground(TypeHierarchyLifeCycle.java:275)
	at org.eclipse.jdt.internal.ui.typehierarchy.TypeHierarchyLifeCycle$2.run(TypeHierarchyLifeCycle.java:228)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)


Session data:
eclipse.buildId=4.11.0.I20190307-0500
java.version=1.8.0_202
java.vendor=Amazon.com Inc.
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=de_DE
Framework arguments:  -product org.eclipse.epp.package.jee.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product -clean

This is a continuation of log file C:\work\gmp_git_workspace\.metadata\.bak_0.log
Created Time: 2019-04-22 12:48:45.352


Steps to reproduce:
Actually a little bit difficult. It does not happen in a new workspace with only an empty (newly created) java project.
Comment 3 Andrey Loskutov CLA 2019-04-22 17:55:26 EDT
Please disable "new" index, it is unfortunately not maintained anymore, see bug 544898.

This bug will be likely closed as "will not fix".
Comment 4 Eclipse Genie CLA 2021-04-12 13:26:28 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2023-04-09 05:21:56 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.