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 181202 - StreamTerm.OutputMonitor threads never finish
Summary: StreamTerm.OutputMonitor threads never finish
Status: RESOLVED FIXED
Alias: None
Product: third-party
Classification: Unclassified
Component: DBX-Gui (show other bugs)
Version: 6.x
Hardware: PC Solaris
: P2 normal (vote)
Assignee: ivan
URL:
Keywords:
Depends on:
Blocks: 181193
  Show dependency tree
 
Reported: 2010-02-25 07:05 UTC by Egor Ushakov
Modified: 2010-06-10 23:49 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 Egor Ushakov 2010-02-25 07:05:58 UTC 
Even after debug session is over StreamTerm.OutputMonitor thread is alive and the more sessions you start the more threads you'll have. It looks like they never finish.
Comment 1 ivan 2010-06-10 23:49:14 UTC 
        http://lessing.sfbay.sun.com/hg/toolshg/rev/24b73cdc16d1

        We need to close the ptys for CmdIo and Pio to make
        the read() in StreamTerm.OutputMonitor to pop out with a -1/exception.
        We do this in ExecutoreUnix.cleanup().
        We're lucky that UnixPty.close() which only closes the
        slave_fd seems to do the trick. I.e. no need to close the
        master_fd allocated by getTty().

        See Evaluation of CR 4892157 for info regarding fd count checks.

        StreamTerm.OutputMonitor's are not used in the remote case.

        Need to make sure that when we switch to nativeexecution that this
        problem doesn't come back to haunt us.

        Incidentally:
        Executor.startIO(Reader, Writer) was dead code so got rid of it
        and members fromTerm and toTerm.