SDK: Modifier destructor

[Anonymous]

I'm working on a plugin that derives from Modifier and noticed something odd. When I delete my modifier (I have a simple test scene with just one object and my modifier applied to it) and call gc() right after that, the destructor for the modifier is not called. In fact, it never gets called, even when I close max.

However, when I delete the object instead of the modifier, and then call gc(), the destructor of my modifier does get called.

Is this the expected behaviour, or am I doing something wrong? Unfortunately I can't post my code here, but hopefully it's just a simple thing that I'm overlooking.

Thanks,

Martijn

[Anonymous]

I should note that the destructor is also NOT called when I first delete the modifier, then the node and then call gc(). Very weird

[Anonymous]

Ok, I've just tested it with a sample modifier (relax) and the same thing happens. This is in 2012 x64 btw, not sure if the issue is caused by something that has been fixed in later versions of max.

Seems like quite a nasty bug though, because it means that any memory allocated by the modifier will not be freed until max is closed, even though the modifier has been deleted from the scene long ago and the garbage collector (should) already have disposed of it.

[Anonymous · Accepted solution]

It works as expected in 2013 so I guess this was a bug in the 2012 SDK (and probably earlier versions)..

[Anonymous]

This like it is not solved for a object plugin in 3ds max 2016.  The same problem.