0

I just started testing my game app on a new Samsung Galaxy S6. It kept crashing with out of memory errors in the log. My app normally uses about 215M and worked fine with the Galaxy S4 mini, Galaxy Tab S3, and Galaxy Tab S4, which have heaps of 256+M, 512+M and 512+M respectively. The Galaxy S6 has a heap of 536M. After cutting down my bitmap sizes to where I could get the Galaxy S6 to run the app, I got the following on the device monitor for heap use of the various devices.

Galaxy S4 mini, Galaxy Tab S3, and Galaxy Tab S4: enter image description here

Galaxy S6 (Lollipop): enter image description here

Why does the newer device use 4 times the heap of the other devices?

Floern
  • 33,559
  • 24
  • 104
  • 119
Androidcoder
  • 4,389
  • 5
  • 35
  • 50
  • 3
    Are you perhaps allocating Bitmaps with a size relative to the dimensions of the screen of the device? Care to share some code that you think is problematic? – Doug Stevenson Mar 19 '16 at 22:08
  • Where are the images coming from? If they are drawable resources, what directory (or directories) do you have them in? – CommonsWare Mar 19 '16 at 22:16
  • You have 1-byte array of size 375 MB, Android stores `Bitmap`s in a byte array. Check this out http://gokhanarik.com/android-background-image-high-memory-usage-issue/ – Gokhan Arik Mar 19 '16 at 22:29
  • I use bmp_stars[0] = BitmapFactory.decodeResource(getResources(), R.drawable.starst0,options); – Androidcoder Mar 19 '16 at 23:27
  • I use bmp_example = BitmapFactory.decodeResource(getResources(), R.drawable.example,options); for decoding bitmaps. i change the options value depending on device heapsize. Looking at your responses (especially thanks for article on screen resolution memory effects Gokhan), i expect the error is due to the increased screen density of the S6: 2-3 depending on the run (don't ask me why) with screenWidth 1920 screenHeight 1080. the galaxy S4 min in comparison has density 1.5 with screenWidth 960 screenHeight 540. Next project is how to fix code for screen density. – Androidcoder Mar 19 '16 at 23:33

1 Answers1

2

It turns out the issue was something being done on the device end, not mentioned in the documentation on supporting different screen sizes here: http://developer.android.com/training/multiscreen/screensizes.html. According to an insightful article by Gokhan Arik, 'Android background image high memory usage issue' at http://gokhanarik.com/android-background-image-high-memory-usage-issue/, referencing a CommonsWare answer to a question similar to mine here: Why does my 160kb app background become 49 MB at run time?, high density devices will resize images stored in a generic 'drawable' folder to a much greater size to match the higher screen resolution, by 4x in my case.

The simple solution was to put all my bitmaps (many several hundred KB in size) into a folder named 'drawable-nodpi', and deleting the old 'drawable' folder. I wish I knew about this issue before I could finally afford a density 3 device to test on.

One drawback to this I recently found is that Google Play will no longer consider your device 'designed for tablets' when you don't have several drawable folders for different screen densities. So incredibly, you may have to create empty ones to not lose this designation.

Community
  • 1
  • 1
Androidcoder
  • 4,389
  • 5
  • 35
  • 50