I am using latest spine-csharp and spine-xna with Xamarin Studio developing iOS apps. I tried updating to latest source in the hope it would fix my problem but it didn't :-(
I am doing an interactive book. Each page is set up with its own background image (drawn just using SpriteBatch) and a set of spine animations. I have a ContentManager, SkeletonRender, Skeleton and Atlas on each page. I should only have a couple of pages in memory at a time, so I want to make sure I free any pages not currently in use.
If I take two pages and scroll back and forth between them, I get a memory warning after say 30 transistions back and forth and program eventually crashes. If I remove all the Spine stuff, I can transition back and forth as long as I want so I am happy I am unloading my rather large background images correctly.
As soon as I have the following in my LoadContent:
_atlas = new Atlas("Content/File.Atlas", new XNATextureLoader(GraphicDevice));
And this in my Unload:
_atlas.Dispose;
_atlas = null;
I am having a problem. I go back to only being able to do a limited number of transitions before crashing.
That does make it seem like a Spine issue doesn't it? I don't like raising issue of memory leaks in case its something in my code but I have spent hours going through my code, its late and my brain is going to mush. As far as I can see it's something in Spine but I haven't been able to spend any time going through the source.
Any suggestions?
BTW am loving Spine. Got some awesome animations for my book which I will load into Showcase forum at some stage but this issue is holding me up.