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 17211 - IDE freezes when writing to output window
Summary: IDE freezes when writing to output window
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P1 blocker (vote)
Assignee: akemr
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-11-01 18:20 UTC by Petr Jiricka
Modified: 2008-12-22 23:53 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Stack trace when the IDE was frozen (99.58 KB, text/plain)
2001-11-01 18:24 UTC, Petr Jiricka 		Details
StackOverflowError (88.38 KB, text/plain)
2001-11-01 18:25 UTC, Petr Jiricka 		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 Petr Jiricka 2001-11-01 18:20:46 UTC 
Build 20011026-1336.

When executing a class with internal execution, the IDE froze for several 
minutes, after which a StackOverFlowError was thrown.

Attaching stack trace while the IDE was locked and the exception.
Comment 1 Petr Jiricka 2001-11-01 18:24:39 UTC 
Created attachment 3232 [details]
Stack trace when the IDE was frozen
Comment 2 Petr Jiricka 2001-11-01 18:25:56 UTC 
Created attachment 3233 [details]
StackOverflowError
Comment 3 akemr 2001-11-02 08:30:25 UTC 
Reassign to me. It's terminal emulator bug.
Comment 4 akemr 2001-11-02 08:39:35 UTC 
Fixed in main trunk.

Ivan used System.out.println (only if term get some unrecognized 
control sequence), which can cause StackOverFlowError.

Anyway, Petre, could you send me this class (you tried to execute) - 
I would like to investigate this "unrecognized control sequence?" 
problem..
Comment 5 Marian Mirilovic 2001-12-12 12:47:28 UTC 
verified in [nb_release330](200112102331)
Comment 6 Quality Engineering 2003-07-01 16:21:27 UTC 
Resolved for 3.4.x or earlier, no new info since then -> closing.