plonk42 / jediterm Goto Github PK

Running Java7 on Windows 7, resizing the terminal often lead to a display freeze (cursor is not blinking anymore, entered chars are not displayed).
Resizing again may (or may not) make the display updating again.

Not sure if we handle properly this.
Sometimes the terminal try to display the BOM char as an actual char, when it should probably not.
Maybe we have to simple clean the input stream from BOM char.

See : http://www.rgagnon.com/javadetails/java-handle-utf8-file-with-bom.html

j7u45 introduced a more restrictive check for jars security attributes (codebase and permission) when using jnlp deployment
When security level is set to "high" (default), it only gives some warnings (see below).
When "very high" is selected, the application won't start.

Missing Permissions manifest attribute for: http://.../jediterm/guava-14.0.1.jar
Missing Codebase manifest attribute for: http://.../jediterm/guava-14.0.1.jar
Missing Permissions manifest attribute for: http://.../jediterm/jsch-0.1.50.jar
Missing Codebase manifest attribute for: http://.../jediterm/jsch-0.1.50.jar
Missing Permissions manifest attribute for: http://.../jediterm/jzlib-1.1.1.jar
Missing Codebase manifest attribute for: http://.../jediterm/jzlib-1.1.1.jar
Missing Permissions manifest attribute for: http://.../jediterm/log4j-1.2.14.jar
Missing Codebase manifest attribute for: http://.../jediterm/log4j-1.2.14.jar

The first thing to check is if new versions of considered libs include or not these attributes.

ESC[ P s Z

See : http://stuff.mit.edu/afs/sipb/user/daveg/ATHENA/OldFiles/SIPB/ATHENA/Info/backtab-howto.txt

This is pretty obscure, but we've experienced a lot of issue when resizing the terminal window.
It is more visible when the window manager triggers resize event as the user drags the border (some window manager only trigger one event, when the user release the mouse button).

I'm convinced this is a race condition between Swing EDT and the emulator thread (maybe a missing synchronization in the backbuffer, or something similar?)

Sometimes, when things go really wrong, we get :

java.lang.ArrayIndexOutOfBoundsException
    at java.lang.System.arraycopy(Native Method)
    at com.jediterm.terminal.display.BackBuffer.resize(BackBuffer.java:132)
    at com.jediterm.terminal.ui.TerminalPanel.requestResize(TerminalPanel.java:463)
    at com.jediterm.terminal.display.JediTerminal.resize(JediTerminal.java:916)
    at com.jediterm.terminal.TerminalStarter$1.run(TerminalStarter.java:82)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
    at java.lang.Thread.run(Thread.java:662) 

When some lines are displayed (and the scroll buffer is not empty??), resizing the terminal to a smaller height (not sure if that height is linked to the number of lines displayed, or to the scroll buffer size) can blow up the display.

The cursor is moved higher than it should, lines are not erased properly, and sometimes we get :

0 [Connector-Local] ERROR com.jediterm.terminal.display.BackBuffer  - Attempt to erase characters in line: -2