The original data is filtered on server side. And in the original application I use "xml" format, not "e4x". No leaking.
The test files: It's a large file, yes. It consumes a lot of memory. But it's for testing. That's why you can see the leaking in seconds. But... If you test the program with e4x and leaktest.xml it does not leak. And leaktest.xml is a LARGE file. By the way... Thanks for your reply! I really appreciate it. :) Lacito --- In [email protected], "Paul DeCoursey" <[EMAIL PROTECTED]> wrote: > > I kind of doubt it's a leak. It's a large file and it's going to > consume a lot of memory. An XML file larger than a 100k isn't going > to perform well using DOM or E4X kinds of operations. I think you'd be > better off doing filtering operations on the server using XSLT perhaps > or some other stream based method. Keep in mind that an XML file > stored in memory for an E4X operation will take up probably 5-10 times > more memory than the document size. Add on top of that some overhead > for the actual E4X operation and it could easily start adding up into > the hundreds of megs. > > --- In [email protected], "lacito.domingo" > <lacito.domingo@> wrote: > > > > Hello, > > > > There is a new pbentries.xml file. I have replaced double acute O > with W. > > > > You can download it from: > > > > http://www.actionscript.org/forums/showthread.php3?t=127834 > > > > And it leaks, too. :( > > > > Thanks, > > > > Lacito > > >
