Using Rotate Manipulator

May 30, 2013 at 12:11 PM
Hi,
wanted to use a RotateManipulator in my application to rotate a Model (CubeVisual3D) all the time.

Now my problem is that I can see in Task-Manager that the memory usage of my application is always increasing as long as the cube is rotating.

Is this normal behaviour or am I missing something here?

Would be glad for any advice how to solve this problem.
Coordinator
Jun 8, 2013 at 5:20 AM
Can you try to run a memory profiler on your application to check whether there is an error in this library or in your application?
The RotateManipulator should just modify the transform of the cube, I don't expect a memory leak here.
Jun 16, 2013 at 7:47 PM
I have spent now lot of time for finding the poblem causing the memory leak.
Now I know that the problem is not the rotate manipulator.
Everytime I'm using basic transformation like this with helixtoolkit
var g = new Transform3DGroup();
g.Children.Add(rotateTransform);
the problem is occuring.

I don't see the problem if I'm defining the rotation transformation in xaml like that:
                     <Transform3DGroup>
                            <RotateTransform3D>
                                <RotateTransform3D.Rotation>
                                    <AxisAngleRotation3D Axis="0,1,0" Angle="{Binding RotationAngle}"/>
                                </RotateTransform3D.Rotation>
                            </RotateTransform3D>
                        </Transform3DGroup>
I don't know why but it is like that.
Think I have to find a workaround for my problem.

Anyway, thanks for the great helixtoolkit!

BR
ftp25
Apr 15, 2014 at 10:20 AM
I am having the same issue as ftp25.
When I perform any camera gesture (zoom/rotate/pan) the amount of memory used by the application jumps by ~450MB.
I ran ANTS memory profiler on the application and it showed that all these extra memory is categorized under "Unmanagad Memory" and no further details where given by the profiler regarding this.
What could be the issue and what should I investigate?
Coordinator
Apr 29, 2014 at 8:27 AM
I guess this is due to how WPF works internallly. Please let us know if you find any issues. Is the memory released later? It does not continue to increase, right?