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 186173 - OutOfMemoryError while running tests in internal terminal
Summary: OutOfMemoryError while running tests in internal terminal
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: execution (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: Andrew Krasny
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-14 15:46 UTC by Alexander Pepin
Modified: 2010-05-17 13:08 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 Alexander Pepin 2010-05-14 15:46:58 UTC 
The error occurs in tests if they use internal terminal:
SEVERE [org.openide.util.Exceptions]
java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(Unknown Source)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
	at java.util.concurrent.FutureTask.get(Unknown Source)
	at org.netbeans.modules.terminal.ioprovider.Task$ValueTask.get(Task.java:102)
	at org.netbeans.modules.terminal.ioprovider.TerminalInputOutput.getErr(TerminalInputOutput.java:678)
	at org.netbeans.modules.nativeexecution.api.execution.NativeExecutionService$1.call(NativeExecutionService.java:145)
	at org.netbeans.modules.nativeexecution.api.execution.NativeExecutionService$1.call(NativeExecutionService.java:123)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
[catch] at org.netbeans.modules.nativeexecution.support.NativeTaskExecutorService$2.run(NativeTaskExecutorService.java:79)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1415)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1954)
Comment 1 Alexander Pepin 2010-05-14 16:08:24 UTC 
INFO [nativeexecution.support.logger]: Error occurred: java.lang.OutOfMemoryError: Java heap space
Comment 2 Alexander Pepin 2010-05-14 16:08:59 UTC 
INFO [nativeexecution.support.logger]: Error occurred: java.lang.OutOfMemoryError: Java heap space
SEVERE [org.openide.util.Exceptions]
java.lang.InterruptedException
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.doAcquireSharedInterruptibly(Unknown Source)
	at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireSharedInterruptibly(Unknown Source)
	at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
	at java.util.concurrent.FutureTask.get(Unknown Source)
	at org.netbeans.modules.terminal.ioprovider.Task$ValueTask.get(Task.java:102)
	at org.netbeans.modules.terminal.ioprovider.TerminalInputOutput.getErr(TerminalInputOutput.java:678)
	at org.netbeans.modules.nativeexecution.api.execution.NativeExecutionService$1.call(NativeExecutionService.java:145)
	at org.netbeans.modules.nativeexecution.api.execution.NativeExecutionService$1.call(NativeExecutionService.java:123)
	at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
[catch] at org.netbeans.modules.nativeexecution.support.NativeTaskExecutorService$2.run(NativeTaskExecutorService.java:79)
	at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1415)
	at org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:1954)
Comment 3 Andrew Krasny 2010-05-14 19:25:29 UTC 
I will look into this. 
The problem seems to be in a native part of the pty support (linux-specific).

and... is it really a P2?
Comment 4 soldatov 2010-05-17 08:28:55 UTC 
This exception appears on my linux machine if I create Welcome project, select "Internal Terminal" mode and launch project
Comment 5 Andrew Krasny 2010-05-17 09:34:52 UTC 
cause is known. will commit fix shortly
Comment 6 Andrew Krasny 2010-05-17 13:08:27 UTC 
The problem was in issue 186245. So the input was closed before an information about pty was put into the stream. Another bug was that this situation was not properly handled on the java side.

the later is fixed with:
http://hg.netbeans.org/cnd-main/rev/38baa2fb53a0