This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 226643 - ArrayIndexOutOfBoundsException: 1024
Summary: ArrayIndexOutOfBoundsException: 1024
Status: RESOLVED DUPLICATE of bug 226642
Alias: None
Product: platform
Classification: Unclassified
Component: Autoupdate (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-25 11:29 UTC by Jan Lahoda
Modified: 2013-02-25 15:44 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter: 198993

Attachments
stacktrace (4.18 KB, text/plain)
2013-02-25 11:29 UTC, Jan Lahoda 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Lahoda 2013-02-25 11:29:51 UTC 
Build: NetBeans IDE 7.3 (Build 20130223-93e87decaddf)
VM: OpenJDK 64-Bit Server VM, 25.0-b18, OpenJDK Runtime Environment, 1.8.0-internal-lahvac_2013_02_19_11_40-b00
OS: Linux

User Comments:
jlahoda: Trying to install the FindBugs plugin.




Stacktrace: 
java.lang.ArrayIndexOutOfBoundsException: 1024
   at java.util.IdentityHashMap$Values.toArray(IdentityHashMap.java:1114)
   at java.util.IdentityHashMap$Values.toArray(IdentityHashMap.java:1098)
   at java.util.ArrayList.<init>(ArrayList.java:151)
   at com.google.common.collect.Lists.newArrayList(Lists.java:119)
   at com.google.inject.internal.Initializer.injectAll(Initializer.java:94)
   at com.google.inject.internal.InternalInjectorCreator.injectDynamically(InternalInjectorCreator.java:174)
Comment 1 Jan Lahoda 2013-02-25 11:29:53 UTC 
Created attachment 131826 [details]
stacktrace
Comment 2 Jan Lahoda 2013-02-25 12:02:38 UTC 
One thing I did not notice originally is that I was running on a relatively recent build of JDK8. Does not happen on JDK 1.7.0_11.
Comment 3 Jan Lahoda 2013-02-25 15:44:14 UTC 
I took a better look at the stacktraces in here, and in bug #226642, and they are apparently the same in the sense that a not-thread-safe map is being accessed from multiple threads.

*** This bug has been marked as a duplicate of bug 226642 ***