If an executing program generates high volume of output to STDOUT, the IDE does not respond to user actions (#3084). Occasionally, it even hangs and a series of ArrayIndexOutOfBoundExceptions is gen
Internal/External execution switch makes a difference in this case. During internal execution no output is captured in the Output Window until the program is finished (if ever). During external execut
ion, the Output Window is updated, but the update interval gets longer and longer until updating stops completely.
JDK 1.3rc1 seems to be a little less prone to this problem than JDK 1.2.2.
See the attached log file and the source file used to generate the problem.
Maybe we could reimplement the output window completely to refresh its state
only once a time? At begining once a 200ms, then 400ms, 800ms, 1600ms, etc. By
doing this threads frequently writing to output would be refreshed less often,
but the IDE would not hang itself.
Priority is changed to P4 (normal).
I have made painting of the redirected output much faster.
Paints are now batched.
Results seems good for print out of 10000 lines - 3 seconds
in internal exec/12 seconds in external exec.
Should be better with term?
verified in nb3.4
Resolved for 3.4.x or earlier, no new info since then -> closing.
moving terminal emulator issues to terminalemulator component.
To see the correct version and target milestone of this issue look at Issue