[ANDROID] Memory management issue?

3 posts / 0 new
Last post
[ANDROID] Memory management issue?


First of all, I would like to say thanks to Dcfedor for such an awesome game. Got it on Steam a while ago and, although I haven't had much time to play it, I have enjoyed the gameplay, the ambient and the story. So much that I am considering to purchase it on Android, so that I can play it on the go.

However, I'm facing some issues on the Android demo version. In detail, I'm on a Oneplus One device, Android 6.0.1. The app is v1.21.d Mobile b4400.

Usually, the game crashes to home screen (no freezing) when tinkering with the inventory. After some tests (and invaluable help from @Marc13Bautista, thanks too BTW), I have been able to reproduce the crash many times and it ALWAYS happens when I put items into the crafting grid. Then, it seems to take a little time for the game to "think" before showing the possible results of the crafting. Sometimes it crashes and sometimes not but, when it does, it is always at this point.

I believe it could be some memory management issue, but I can't be sure. In fact, I don't even know if it is a problem of the game or my device, but any help will be appreciated.

Thanks in advance for your help and attention.

Hi Midnightkid,

Thanks for the info and testing! I think you're right that it's crafting, though it seems like it's due to a null reference error instead of memory. There's a patch pending with a fix for this, and I hope to have it launched soon.

In case you're interested in the gory details:

It turns out that non-empty containers that are consumed in crafting have their contents cloned, the clones placed on the ground, and the original contents destroyed.

However, those original items are still referenced in the game (UI, crafting screen proxy items, etc.), so pretty much anything attempted next in game causes a null pointer.

Confusingly, this didn't happen all the time, with any non-empty container and recipe. I only stumbled upon it in a late-game save while attempting to quick recipe a fire and then a roasted meat on a stick.

Trying to recreate this scenario didn't work. But this late-game save crashed 100% of the time when making a fire and roasting meat in that order.

The fix appears to be as simple as not destroying the contents, not bothering with cloning, and just adding those originals to the ground (since they were originally in the container). All seems good now, and I don't think this affects memory leaks, since no new items are created. (Might even be faster/slimmer now!)

So, fingers are crossed!

Dan Fedor - Founder, Blue Bottle Games

Hi Dcfedor,

Thanks for your complete answer and explanation. I will be waiting for your next update and, of course, supporting your awesome work. Please, keep it up.

I wish you best of luck with the mobile release. You deserve it! :).