We now have a workaround for the memory leak in our application. Calling qx.io.remote.Request directly removed the leak and provided a working solution.
This would suggest that the memory leak is in the qx.io.remote.Rpc class, as the leak only appears when using this class. The earlier tests I made using XMLHttpRequest direct were misleading as the computer I was testing on had some issues with incorrect dll versions. Testing the direct calls to XMLHttpRequest on a correctly installed IE6/7 produced no memory leaks. -- View this message in context: http://n2.nabble.com/Memory-leak-in-IE7-using-qx.io.remote.Rpc-in-0.8.2-tp2686912p2733810.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
