On Tue, 2011-08-02 at 20:39 +0200, Moritz Struebe wrote:
On 2011-08-02 20:09, John A. Sullivan III wrote:
To summarize, when using firefox/iceweasel in X2Go, the browser frequently hangs for between 16 and 20 seconds. All other applications work perfectly fine, accept input, and display output, but the browser window remains frozen. Once it unfreezes, all input and output is processed, e.g., typed letters are displayed and tab clicks are executed. It appears to happen in AJAX intensive sites (Zimbra, GMail, GLPI) but this is not definitive.
The smells like Nagle, but who knows.... Can you give information on your connection parameters. For example: I'm in a LAN and noticed that I get the best results using no compression (rgb) - but one in a while there are small errors in the disply (e.g. an immage not being updated correctly) - opposed to png. I also have the gnome-system-monitor-applet running, therefore data is sent continuously. I would also be interested whether the whole screen hangs (e.g. including the system monitor) or only the single Applicaiton. Maby you cold start xkbwatch and see, whether the keystrokes (e.g. shift ) still arrive at the server.
<snip> I believe we can rule out Nagle or anything on the network layer because it only affects the single application. If it were Nagle, the entire connection would freeze while it buffered responses and this would typically appear as a slight lag I believe - not a 20 second delay.
The single application feature is the strange part. This is a WAN environment using 16m-png-jpeg. While the browser is hung, all other applications interact appropriate so data is being transmitted.
xkbwatch sounds like an interesting idea. I have never used it but will find out how. Thanks - John