1.1.06.1 memory leaks and crashes?

[Scott Andrew]

I have a project that uses quite a few large (4094x4094) PNG sprite sheets for our retina assets. This is a book and our sheets are divided into pages/screens since there are quite a few full screen images. With 1.1.06.1 I am seeing a lot of crashes after navigating around the crashes look like:

03-22 18:54:52.203  2834  2871 W v       : *** cannot allocate region of size 16777216

03-22 18:54:52.203  2834  2871 W v       : *** set a breakpoint in malloc_error_break to debug

03-22 18:54:52.203  2834  2871 W v       : *** cannot allocate region of size 16777216

03-22 18:54:52.203  2834  2871 W v       : *** set a breakpoint in malloc_error_break to debug

That is the size of an image. I have since moved back to 1.1.04.1 and all appears to be fine. We aren't getting any crashes.

[Zac Bowling]

Can you set a breakpoint on the malloc helper function in GDB and print a backtrace?

Use “apportable debug” when you launch your app. Then in the gdb prompt when it comes up use the command “b malloc_error_break” to create a breakpoint and then use “c” to continue. When the app breaks, you can use “bt” to print the backtrace to see the method calling malloc with such a huge size.

You can post the stacktrace here and we can try and help find the culprit.

Thanks!

Zac Bowling
Engineering - Apportable
http://apportable.com/

> --
> You received this message because you are subscribed to the Google Groups "Apportable discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to apportable-disc...@googlegroups.com (mailto:apportable-disc...@googlegroups.com).
> For more options, visit https://groups.google.com/d/optout.

[Scott Andrew]

It wouldn’t let me set it.. Kept telling me it was undefined.

Scott

[Zac Bowling]

Hmm. That should be there at main. You can set a future breakpoint with “fb” instead of “b” and when that symbol is loaded it will fire.

Zac

[Scott Andrew]

I’ll need to check it out later next week. I am under deadline for monday..

Scott

[Scott Andrew]

We ended up having to change what scale we consider 2x.. We had 130% from an old project that used PVRs everywhere we since moved to PNGs and the scaling is better. I have bumped it up to 150% and that got rid of performance issues we were seeing on the nexus 7 and the crashes. When a jumped down a version it would eventually crash but give me video memory issues.

>>>> To unsubscribe from this group and stop receiving emails from it, send an email to apportable-discuss+unsub...@googlegroups.com (mailto:apportable-discuss+unsub...@googlegroups.com).

[Diego]

Hi there.

we are in the last steps of releasing our Android app, and facing exactly the same issue with memory not being released. It started with version 1.1.06 of Apportable. Versión 1.1.04.01 seems to release memory as expected.

We've created a very very simple app to probe it: it just adds a UIImageView to the window, and then replaces the image with a new UIImage each time the BACK button is pressed. You should see different background colours as you press the BACK button on the device. 

Although some memory is released, a big part is not, and the program will crash after a few taps on BACK button. 

Could you please look into this issue asap? 

Please let us know if you need anything else from us to reproduce the issue; and of course, if there is any workaround to this, we would like to know as it is the main reason we are holding the Android release. 

Sample project: https://www.sendspace.com/file/9ep6ne

Thanks,

Diego