Hi all, (from a previous message)
cbrown-2 wrote: > > 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. > cbrown-2 wrote: > > Here is a code snippet with the relevant information for the workaround > using > qx.io.remote.Request. > I haven't (yet, at least) found the time to dig this down but, IMHO, this was something deserving a proper investigation: RPC is one of the most powerful qooxdoo features and probably one of the most used (naturally, I'm mostly guessing in terms of "used"). If a leak is there, it's probably affecting the long running qooxdoo applications with server communication (almost all?)... I wonder if this is affecting the legacy branch (0.7.x) also... Thanks, cbrown, for sharing your (partial) solution, Helder Magalhães -- View this message in context: http://www.nabble.com/Memory-leak-in-IE7-using-qx.io.remote.Rpc-in-0.8.2-tp23206022p23295875.html Sent from the qooxdoo-devel 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
