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.
Build: NetBeans IDE 7.4 Beta (Build 201307092200) VM: Java HotSpot(TM) 64-Bit Server VM, 23.21-b01, Java(TM) SE Runtime Environment, 1.7.0_21-b11 OS: Linux User Comments: rptmaestro: Double clicked on a word in the "Report Problem" details field. Stacktrace: java.lang.InternalError: java.io.IOException: Stream closed at java.text.BreakIterator.createBreakInstance(BreakIterator.java:620) at java.text.BreakIterator.getBreakInstance(BreakIterator.java:565) at java.text.BreakIterator.getWordInstance(BreakIterator.java:465) at javax.swing.text.Utilities.getWordStart(Utilities.java:641) at javax.swing.text.DefaultEditorKit$BeginWordAction.actionPerformed(DefaultEditorKit.java:1750) at javax.swing.text.DefaultEditorKit$SelectWordAction.actionPerformed(DefaultEditorKit.java:2163)
Created attachment 137233 [details] stacktrace
SEVERE [org.openide.util.Exceptions] java.lang.InternalError: java.io.IOException: Stream closed at java.text.BreakIterator.createBreakInstance(BreakIterator.java:620) at java.text.BreakIterator.getBreakInstance(BreakIterator.java:565) at java.text.BreakIterator.getSentenceInstance(BreakIterator.java:546) at com.sun.tools.javadoc.DocLocale.<init>(DocLocale.java:104) at com.sun.tools.javadoc.DocEnv.<init>(DocEnv.java:146) at org.netbeans.modules.java.source.JavadocEnv.<init>(JavadocEnv.java:102)
I see two possible causes, and unfortunately I don't see a way to determine the real cause without the start-up header of the log, which the exception reporter neglected to include. The two causes are: 1. JDK placed in a directory ending with an exclamation mark ('!'). Filled as CR 8020712 to JDK. If this is the reason, then I don't see a way for us to do anything about that. Simply place your JDK to a directory whose name does not end with '!'. 2. The process is out of file descriptors. Unfortunately, the only way for me to even attempt to evaluate which module may be the culprit is to have the list of opened file descriptors, but I don't have such a list. So if point "1." does not hold for you, please provide the list of opened file descriptors, i.e. the output of: ls -l /proc/<IDE's-process-number>/fd Thanks.
*** Bug 240913 has been marked as a duplicate of this bug. ***
*** Bug 244791 has been marked as a duplicate of this bug. ***
*** Bug 244794 has been marked as a duplicate of this bug. ***
*** Bug 251006 has been marked as a duplicate of this bug. ***