Hi Mike, I think it's because Nuke keeps your Op instance for 'Undo', this is also why doing some thing in Op's destructor is not reliable, correct me if I misunderstood.
Shing On Wed, May 16, 2012 at 10:19 PM, mike.artixels < [email protected]> wrote: > ** > Jon, > > Thanks a lot for these clarification especially about aggressive caching. > I have a recent experience that after I deleted a DAG node, there is still > one instance not deleted, I discovered this by accident because my node > prints debug message when Nuke prompts it via the Memory class > freeCallback(). So is this also an expected case ? > > As my Op requires internal memory buffer for processing, so I guess it's > not safe to share common memory buffers among them, right? as they might be > doing rendering at different contexts ..... > > Thank you, Jon. > > Best, > > Mike > > _______________________________________________ > Nuke-dev mailing list > [email protected], http://forums.thefoundry.co.uk/ > http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev > >
_______________________________________________ Nuke-dev mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
