Page 4 of 4 FirstFirst 1234
Results 31 to 34 of 34

Thread: Collada DOM memory leak issue.

  1. #31
    Junior Member
    Join Date
    Sep 2005
    Posts
    6
    glad you found the problem!

    I did get quite lot of other leaks after I do this:

    pCollada->load(url);
    domCOLLADA *dom = pCollada->getDom(url);
    dom->resolveAll();
    DeIndex(pCollada);
    // Load all the image libraries
    for ( u64 i = 0; i < dom->getLibrary_images_array().getCount(); i++) {
    ReadImageLibrary( dom->getLibrary_images_array()[i] );
    }
    delete pCollada;

    DeIndex() and REadImageLibrary() code are from COLLADA_RT sample.

    have you run VLD on all your test programs?

  2. #32
    Senior Member
    Join Date
    Jan 2006
    Location
    Foster City, CA
    Posts
    540
    I did get quite lot of other leaks after I do this
    Yeah, RT is leaky as hell. I just filed a bug on this yesterday in fact. Based on the leak report attached to that bug I get the impression that all the ReadWhatever functions leak memory.

    Unfortunately our RT developer is on vacation for the rest of the year. I'm hard at work on a DOM 2.0 release and I'm not in a position to fix these leaks now. I might be able to look at it sometime, but I can't make any promises. It shouldn't be too hard to fix these yourself if you're so inclined.
    have you run VLD on all your test programs?
    No, just on my little sample program that I used to track down the libxml leak. Frankly, VLD is a pain to use because it requires modifying your source, so I'll probably only use it if someone reports a leak that I can't catch with Valgrind. Valgrind reports no leaks on our automated test suite, which exercise the DOM pretty well, so I don't think there are many (any?) DOM leaks anymore.

    Steve

  3. #33
    Junior Member
    Join Date
    Nov 2007
    Posts
    10
    any update on possible fix that might be coming up regarding this [in any future release] ?

  4. #34
    Senior Member
    Join Date
    Jan 2006
    Location
    Foster City, CA
    Posts
    540
    Are you talking about the RT memory leaks? I believe our RT guy is working on fixing them now. If it's a big problem for you, keep in mind that they should be fairly easy to fix yourself.

    Steve

Page 4 of 4 FirstFirst 1234

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •