In the new output2 the process output is grabbed
using the nio API. The current JDK on OS/2 does
not allow some nio operations on STDIN/STDOUT/STDERR.

Due to this the following block:

                    try {
                        contents =
ch.position(0).map(FileChannel.MapMode.READ_ONLY,
                            0, mappedRange);
                        this.contents = contents;
                    } catch (IOException ioe) {
                        ioe.printStackTrace();
                       
ErrorManager.getDefault().log("Failed to memory
map output file for " + //NOI18N
                                "reading.  Trying
to read it normally."); //NOI18N
                        //If a lot of processes
have crashed with mapped files (generally when
testing),
                        //this exception may
simply be that the memory cannot be allocated for
mapping.
                        //Try to do it non-mapped
                        contents =
ByteBuffer.allocate((int) mappedRange);
                        ch.position(0).read(contents);
                    }

always continues in the catch block. So a lots of
exception logs are generated which makes the
output window scrolling slow.

Could be the exception logging turned off in this
code (if at least for OS/2)?