Community
Participate
Working Groups
Using I20060103-0800 + HEAD content. With runtime patched with HEAD content or eclipse session self-hosted I systematically get an OOME while cleaning org.eclipse.jdt.core project. Here's the stack trace: SimpleLookupTable.<init>(int) line: 36 State.read(IProject, DataInputStream) line: 254 JavaBuilder.readState(IProject, DataInputStream) line: 114 JavaModelManager.readState(IProject) line: 2226 JavaModelManager.getLastBuiltState(IProject, IProgressMonitor) line: 1267 JavaBuilder.getLastState(IProject) line: 356 JavaBuilder.build(int, Map, IProgressMonitor) line: 139 BuildManager$2.run() line: 593 SafeRunner.run(ISafeRunnable) line: 37 Platform.run(ISafeRunnable) line: 785 BuildManager.basicBuild(int, IncrementalProjectBuilder, Map, MultiStatus, IProgressMonitor) line: 168 BuildManager.basicBuild(IProject, int, ICommand[], MultiStatus, IProgressMonitor) line: 202 BuildManager$1.run() line: 231
Introduced with bug 76266. Need to realign read/write operations on access restrictions templates.
Created attachment 32527 [details] Fix restrictions read/write
Changed org.eclipse.jdt.internal.core.builder.State to: - raise the version number (again - apologies); - get read/write in sync for restrictions.
I suggest that the verification be made on the source code.
This fix triggers a full build of the workspace.
*** Bug 122888 has been marked as a duplicate of this bug. ***
Verified for 3.2 M5 using build I20060214-0010