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.
Every time I go through a compile cycle, a new set of output tabs gets created, e.g. 'Compile (, Debugger console), 'Process Output. This soon leads to a cluttered output window. Output tabs should get reused.
This works for me - if you're seeing "process output" it sounds like you're not just compiling, but executing something. Are you sure the process you executed has really stopped? They should be reused if the last process that used those tabs has ended. If the process hasn't, then the tabs will stay open. You can find out if processes are still running in the Execution window. Note that if your program is a JFrame, just closing the JFrame does not necessarily end the process, unless its closeOperation is set to EXIT_ON_CLOSE. NetBeans form editor will generate a window listener that calls System.exit() when you close it. Otherwise the JVM will sit there forever doing nothing until either it is explicitly killed (you can right click items in the Execution window to do that), or its parent process exits.
Could it be possible NB does not catch an application being aborted in the debugger? I will check later today whether this only happens when you abort the app in the debugger by presing the small red sqaure or also when performing System.exit().
Just found this on nbusers: Betreff: Re: 3.6 beta RFE: Closing windows automatically Absender: David Kafrissen <dkafrissen@yahoo.com> Empfänger: nbusers@netbeans.org Datum: 10.02.04 22:57 In my environment I get a new set of windows every time I debug. Can't it reuse the same set? Everytime I get a new compile, output etc window.
This is a duplicate of another issue - it was already reported - but I'm having trouble locating the issue.
Passing to debugger - this works for exection, probably not a problem in winsys.
*** This issue has been marked as a duplicate of 34828 ***
Verified ... and Closing all issues resolved into NetBeans 6.7 and earlier.