The consequence is that the object was hold in the c++ side but owned by javascript side.
This does not happens when letting Javascript holding every SofaXXX pointer.
The PR fix that for the SofaBaseApplication.
Warning: there is still an issue because of the use of a raw pointer instead of a smartpointer to the object so he can be destructed (when the graph is destroyed for example) but still hold there.
The consequence is that the object was hold in the c++ side but owned by javascript side. This does not happens when letting Javascript holding every SofaXXX pointer.
The PR fix that for the SofaBaseApplication. Warning: there is still an issue because of the use of a raw pointer instead of a smartpointer to the object so he can be destructed (when the graph is destroyed for example) but still hold there.