i've also noticed this, something you could try would be to override _close and either have it clean up the data or at least set the weight on the allocated DD::Image::Memory to 0 so at least nuke will swap it out first (if you're using DD::Image::Memory)
-josh On Mon, Jul 9, 2012 at 1:55 PM, Anders Langlands <[email protected]> wrote: > I'm finding that Nuke will sometimes destroy my Op, and sometimes not. If I > create half a dozen plugin nodes then delete them, maybe 2 will call > MyOp::~MyOp(). Then when I quit Nuke, those destructors still won't be > called. > > In my particular plugin I allocate ~25MB of interprocess shared memory per > Op, so leaving this hanging around is a bit of a deal. Is this something to > do with the undo functionality or something else that I can turn off? Is > there some other hook I can use that *is* guaranteed to be called when an Op > is no longer needed? > > Cheers, > > Anders > > > ----------------------- > Anders Langlands > x8382/+447789206593 > > _______________________________________________ > 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
