Hi Kenneth Can you reproduce this if you stubbed out the remote call, simulating the callback with a setTimeout()? From your descriptions I’m not clear on whether there is a problem in the request handling or the UI code, and if you could show that it has nothing to do with the server request then you could create a playground example to reproduce the problem (which would make it much easier to help)
Also, are you saying that he students with the problem have the _same_ code (client and server) but just their machine hangs? Or functionally similar code written by different people? Regards John. From: Kenneth Tilton <k...@tiltontec.com> Reply-To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net> Date: Wednesday, 21 October 2015 at 20:12 To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net> Subject: Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs And now we descend into the rabbit hole: The students on which the request hangs are the only ones with 17 rows of data. It is the count that corrupts things, not the data, and I can unhang the student by adding or removing data or just by lying when I call _onLoadRowCount and passing 18 if the true count is 17. (16 also works but would hide data from the user.) I did change the block size to see if that flushed the bug, but no luck. Can't wait to see what this is about, but I am no longer worrying about request handling -- from what I have seen it is just that qooxdoo hangs and so the code that would grab the queued request and dispatch it just never runs. Getting close. -kt
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
