Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualNightCreature83

Posted 04 August 2013 - 03:06 PM

The problem is cuased by the GeometryInstance not having a copy constructor and assignment operator but having a destructor that is non trivial. The code just happens to run on fine for a while but as we are using that memory the heap catches a corruption.

 

And the problem is caused by the inline creation of the GeometryInstance in the constructor call to MeshGroup.


#1NightCreature83

Posted 04 August 2013 - 03:02 PM

The problem is cuased by the GeometryInstance not having a copy constructor and assignment operator but having a destructor that is non trivial. The code just happens to run on fine for a while but as we are using that memory the heap catches a corruption.


PARTNERS