Hey, > I am trying to ensure that I dispose of objects properly so I am > generating using the disposer config. You should not take those warnings too serious. Not every warning shows you a memory leak. It shows you more a spot where a memory leak could be.
> One problem I see is that every Xhr prints an error message, > complaining of three fields: > -- Missing destruct definition for '__requestHeaders' in qx.io.request.Xhr > -- Missing destruct definition for '_transport' in qx.io.request.Xhr > -- Missing destruct definition for '__response' in qx.io.request.Xhr > > None of these are not specified in the destructor for either > AbstractRequest or Xhr. However, for _"transport" there is something > along the lines of: > -- var trans = this._transport; > -- trans.dispose(); > > > Questions: > 1) Do I need to take action to dispose of these myself? No. Generally, you have to take care of two things. First, remove all references to the DOM and second, revel all references to the current or global scope. As the .dispose call takes care of that, you don't need to do anything else. > 2) Is this a bug in the framework, or am I misunderstanding something? No, not really. Thats just something hard to detect. Disposing is a complex top and not easy to detect what needs to be disposed and of what the garbage collector can take care of. Thats why those warnings are more hints. Regards, Martin ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
