Big memory leak in new Gideros!

billydb · September 2015

I've been trying to track down a memory leak (with the help of bowerandy's excellent "leaky") and it's been completely mystifying until, as a last resort, i tried downloading an earlier Gideros (2015.04.18) version and bingo! it disappeared.

I tried the release before the last and also old backups of the game (that I know had no memory leaks) but it still had the memory leak so either something is up with the newer versions of Gideros or I'm doing something that is no longer supported/ advised.

I'm using box2d, tntParticles, tilemaps (via a modified TiledAsWorldEditor), 2 global texture packs setup in the main class and, as a framework, ar2rsawseen's Game Template.

Please help!

Thanks

totebo · September 2015

Are you able to remove any of the elements of your game to pinpoint which part causes the leak?

billydb · September 2015

I tried removing the tilemaps, the sound, the texture packs, basically everything except the scenemanager. Even if it is something in my code it doesn't explain why it doesn't happen in earlier Guiders releases, i think

billydb · September 2015

Ill keep trying different versions and see if i can pin down which update makes the difference.

ar2rsawseen · September 2015

One of the things that was upgraded was Box2d, which also caused problems on inter processors on Android

it was upgraded in 2015.06.30

so check if 2015.06.10 works ok for you

billydb · September 2015

I narrowed it down to 2015.08

Everything before that works fine.

Could it be to do with the changes to movieclips? I use a lot of them in my stuff.

ar2rsawseen · September 2015

Interesting, please open issue on Github

billydb · September 2015

Cool. I added an "issue" if that's what you mean? Sorry not too clued up on Git

ar2rsawseen · September 2015

yes, I saw it, thanks

john26 · September 2015

Thanks for narrowing this down. Since we live nearby perhaps I could visit and see the memory leak in person ;-)

yubaro · September 2015

Me too happens to me this and not use box2d. I removing all except the scenemanager and earlier versions did not happen.

john26 · September 2015

May be something to do with graphics. So which operating systems is this happening in? Are you just testing in the desktop player and seeing the memory leak? Does it happen when exported?

billydb · September 2015

Hi john, unfortunately i'm back in Finland, would be great if I could show it you in person. I've now reverted to the earliest version of Gideros on the download page as the 2015.07 version was constantly crashing the player. It's a bit weird but there is a definite leak in the newer versions but it's proving hard to track because of the crashing. Will keep looking. I'm testing on a Mac (although I had the same results in Windows) and on an iphone6 with the Gideros player. Haven't tried an export yet as i get "-fembed-bitcode is not supported on versions of iOS prior to 6.0".

It never rains it pours

totebo · September 2015

Hi @billydb, I can at least help with the bitcode issue. If you export to iOS 6+ in Xcode 7 you'll have to flick the "Enable Bitcode" flag to false (or "No"...) for it to compile.

billydb · September 2015

great thanks totebo

billydb · September 2015

So latest is testing on phone with latest gideros player has the memory leak and installing version from 2015.07 removes it. Tried removing everything except a button graphic and the scenemanager and same problem.

ar2rsawseen · September 2015

So the problem is with Scenemanager?
Which means it is possible with adding/removing Sprite children?

How do you really detect the leak?

billydb · September 2015

A use a class called profiler that shows memory usage and framerate but i cant remember where it came from

ive also used leaky
http://giderosmobile.com/forum/discussion/2645/help-with-memory-leak/p1

I guess its still possible its my code but i assume not as the problem goes away in earlier versions.

john26 · September 2015

The graphics engine has changed a lot recently, it might be that. Vertex Buffer Objects were added which might cause a memory leak in some circumstances. At least they have the potential to do so... @hgy29 can you comment on this?

hgy29 · October 2015

Well VBO shouldn't cause this, since their lifetime is the same as the Sprite which use them. Still every new line of code may introduce bugs. Can't iOS heap profiling tools point us the issue ?

john26 · October 2015

@billydb, thanks for narrowing it down, we'll try to find where the bug is.

billydb · October 2015

Ill do some more testing tonight and try and makensure its not my code:)

Howdy, Stranger!

Categories

In this Discussion

Top Posters

Big memory leak in new Gideros!

Comments

Howdy, Stranger!

Quick Links

Categories

In this Discussion

Top Posters

Big memory leak in new Gideros!

Comments