Screen updates don't always get posted

[GoogleCodeExporter]

On a long-running neatx session, if I do something display-intensive in a 
window, e.g. hold down PageDown while viewing a huge textfile in less using 
gnome-terminal, or run a program that dumps tons of text to the terminal, 
the display updates quickly become infrequent and the window is not updated 
until the NX Client window receives mouse or keyboard input.

In the less example, after holding down PageDown for a few seconds and 
releasing, less appears to stop paging down, but each time the mouse is 
moved or the keyboard is pressed, less scrolls down a few more pages.  Each 
time you press 'q' on the keyboard, it will display one more page of text, 
until the queue of screen updates catches up, and then you will see less 
exit.

Curiously, other screen updates outside the window are fine, e.g. the 
gnome-system-monitor applet continues to update with the correct frequency, 
even while the updates from the gnome-terminal window have frozen waiting 
for external events to wake up whatever is blocking.

I don't know if this bug is with NX Client or with neatx.  How do I tell?  
I don't recall ever seeing this with freenx though.

Original issue reported on code.google.com by luke.hutch on 4 May 2010 at 1:50

[GoogleCodeExporter]

Actually I think what was causing this was one update-intensive app on the 
screen next 
to the terminal window (the gnome-system-monitor application, viewing CPU 
usage, with 
smooth updates enabled, so the graph is constantly smoothly scrolling).  This 
seems to 
create starvation for screen updates from the other window.

Original comment by luke.hutch on 5 May 2010 at 1:21

[GoogleCodeExporter]

Hi,

I had the same problem, but upgrading to the 3.4 version of the nx tools helped 
a lot.

I do not know how you have installed your nx stuff but be warned you might get 
into
other trouble with that version.

I described my problem at the issue 49
(http://code.google.com/p/neatx/issues/detail?id=49). I have just added how to 
solve
that issue.

Greetings,
Theodor

Original comment by erazo...@gmail.com on 17 May 2010 at 12:29