Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>From deployments in the wild, I've found the following devices:</p> <ul> <li><strike>Devices that limit to 16 MiB of java heap (bitmaps are nearly unlimited).</strike></li> <li>Devices that limit to 16 MiB of (java heap + native bitmap storage)</li> <li><strike>Devices that limit to 24 MiB of java heap (bitmaps are nearly unlimited).</strike></li> <li>Devices that limit to 24 MiB of (java heap + native bitmap storage)</li> </ul> <p>24 MiB tends to be the high res devices, and can be detected with Runtime.getRuntime().maxMemory(). There's also 32MiB devices now, and some of the rooted phones have 64MiB by default. Previously, I confused my self several times trying to work out what was happening. I think all devices count bitmaps into the heap limit. But it's wildly difficult to make any sweeping generalizations about the android fleet.</p> <p>This is a VERY nasty issue on Android, and very confusing. This limit and it's behaviors are poorly documented, complicated, and extremely non-intuitive. They also vary across devices and OS versions, and have several known bugs. Part of the problem is that the limits are not precise - due to heap fragmentation, you will hit OOM well before the actual limit and must conservatively leave a meg or two of buffer. Even worse, I've got several devices where there is a native segfault (100% a bug in Android itself) that occurs before you get the java OOM exception, making it doubly important to never reach the limit since you can't even catch the native crash. For more details on my investigations, check out <a href="https://stackoverflow.com/questions/6892676/android-bitmap-limit-preventing-java-lang-outofmemory">this post</a>. In the same post, I explain how to measure usage against the limit and avoid crashes.</p> <p>The size of the java heap is Runtime.getRuntime().totalMemory().</p> <p>There is no easy way to measure the size of the native bitmap storage. The overall native heap can be measure with Debug.getNativeHeapAllocatedSize(), but only the bitmaps count toward the limit (i think).</p>
    singulars
    1. This table or related slice is empty.
    1. POBitmaps in Android
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USDave Dopson
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSince anyone can release their own version of Android, it seems quite believable that there could be versions out there that implement different policies for limiting heap memory, including those that you describe above. CyanogenMod, for example, allows users to set the heap limit themselves, so I don't see why there could not be an OS release that implements the policies regarding limits that you describe. I'd be interested to know whether there are any official guidelines in this regard. If not, then we're subject to the whims of those OS variants.
      singulars
      1. PO
      1. USCarl
    2. CO@Carl. From what I can tell, it's pure chaos. Though in general, the mods and rooted phones tend to increase the heap limits, typically to 64M. The decision to so severely limit Java heap size was brain-dead retarded and results in horrible user experiences.
      singulars
      1. PO
      1. USDave Dopson
    3. COIt does force us as developers to take a hard look at our use of memory. I am presently developing an app that has a very large data set that *must* reside entirely on the heap (because of an intensive search process), and my original String array-based implementation took up 15 MB of heap for that data alone (each String ref in the array takes 32 bytes of data). After nearly hitting the 24 MB limit that a lot of current devices still impose, I designed a custom data structure that takes only 3.5MB to hold exactly the same information. Now my app will run even on a device with a 16MB limit.
      singulars
      1. PO
      1. USCarl
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload