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 228272 - ArrayIndexOutOfBoundsException that I wasn't able to report via the Exception Reporter
Summary: ArrayIndexOutOfBoundsException that I wasn't able to report via the Exception...
Status: RESOLVED DUPLICATE of bug 228156
Alias: None
Product: ide
Classification: Unclassified
Component: Code (show other bugs)
Version: 7.3
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: issues@ide
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-05 05:46 UTC by mienamoo
Modified: 2013-04-05 10:00 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 mienamoo 2013-04-05 05:46:35 UTC 
NetBeans build 201302132200
JDK 7u17 64-bit

When starting up the IDE, I got the exception below. When I clicked the Review and Report Problem button on the Exception dialog, the dialog just went away and I didn't get the opportunity to report it via that mechanism.

I colleague reported the same thing on Windows 8 yesterday.



java.lang.ArrayIndexOutOfBoundsException
	at java.lang.System.arraycopy(Native Method)
	at java.io.PushbackInputStream.unread(PushbackInputStream.java:235)
	at org.netbeans.modules.uihandler.Installer.copyWithEncoding(Installer.java:1458)
	at org.netbeans.modules.uihandler.Installer$Submit.doShow(Installer.java:1634)
	at org.netbeans.modules.uihandler.Installer.displaySummary(Installer.java:1001)
	at org.netbeans.modules.uihandler.Installer.access$400(Installer.java:114)
	at org.netbeans.modules.uihandler.Installer$2Auto.run(Installer.java:576)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1454)
[catch] at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2048)
Comment 1 Marian Mirilovic 2013-04-05 10:00:52 UTC 

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