Memory leak when using hardware skinning

[MattStevens]

Hello,
After 2 weeks of debugging and tracing and profiling I came to the conclusion that using hardware skinning in Ogre 1.7.2 causes memory leak. Not leaks during the use of hardware skinning itself but when loading / unloading resources (material / shaders) that have it enabled.

So what I want to know is, is this fixed in later versions of Ogre ? I checked the changelogs where I could find them, but there was no mention of this issue. Also since we are close to a release, I'm not sure I'll be able to upgrade so I'ld rather fix it in 1.7.2.

If it is not fixed, anyone has tips where I should start looking ? The code seems to be very straight forward and one of the reason it took me so long to spot it (I was convinced hardware skinning couldn't leak). Any help is greatly appreciated, I'll keep you posted with my findings.

- Matt

[MattStevens]

Update on this issue.
The memory leak is not in the hardware skinning, I was wrong. The problem I had was with the shader I made to allow hardware skinning on my mesh. The problem is described in this other thread.
http://www.ogre3d.org/forums/viewtopic.php?f=2&t=70552

While it is not a "leak", I'm pretty sure it is an unintended behavior because you effectively duplicate some resources every time the level resource group is loaded. (See the thread to understand).

Is there a way to prevent resource group switching ? Perhaps we could add a flag to the resource group.

- Matt