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 Dev (Build cnd-main-3557-on-100517) VM: Java HotSpot(TM) Client VM, 14.2-b01, Java(TM) SE Runtime Environment, 1.6.0_16-b01 OS: Windows Vista User Comments: apepin: Steps to reproduce: - create Quote sample on Windows with cygwin - choose Internal terminal asa console type - run the application, run fails due to error while running "pty" - close "pty error" window Result: Exception window appears. Stacktrace: java.lang.NullPointerException at org.netbeans.modules.terminal.ioprovider.Task$GetOut.call(Task.java:489) at org.netbeans.modules.terminal.ioprovider.Task$GetOut.call(Task.java:482) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at org.netbeans.modules.terminal.ioprovider.Task$ValueTask.perform(Task.java:92) at org.netbeans.modules.terminal.ioprovider.Task.dispatch(Task.java:144)
Created attachment 99084 [details] stacktrace
This seems to be a result of Bug 186173 - OutOfMemoryError while running tests in internal terminal and Bug 186245 - output in internal terminal could be lost .. both are fixed (binaries are not commited yet...)
I think the fixes mentioned by Andrew address the "pty error" problem. The NPE looks like a cascade but nevertheless should not happen. I have a hard time figuring how the IO could've gotten into a state as this though. Can one of you, if it's reproducible, take a snapshot at the time the "pty error" dialog is popped up?
Alexander ... what exactly is the error message in the pty window?
It's is Window's message that "pty" failed to start, it's very similar to the problem described in bug #184063. But now, after fixing bug #186173 and bug #186245, it's not reproducible any more.