Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I found this in some more Apple documentation:</p> <blockquote> <h2>Memory Usage for Background Apps</h2> <p>Every app should free up as much memory as is practical upon entering the background. The system tries to keep as many apps in memory at the same time as it can, but when memory runs low it terminates suspended apps to reclaim that memory. Apps that consume large amounts of memory while in the background are the first apps to be terminated.</p> <p>Practically speaking, your app should remove strong references to objects as soon as they are no longer needed. Removing strong references gives the compiler the ability to release the objects right away so that the corresponding memory can be reclaimed. However, if you want to cache some objects to improve performance, you can wait until the app transitions to the background before removing references to them.</p> <p>Some examples of objects that you should remove strong references to as soon as possible include:</p> <h3>Image objects</h3> <p>Large media or data files that you can load again from disk Any other objects that your app does not need and can recreate easily later To help reduce your app’s memory footprint, the system automatically purges some data allocated on behalf of your app when your app moves to the background.</p> <p>The system purges the backing store for all Core Animation layers. This effort does not remove your app’s layer objects from memory, nor does it change the current layer properties. It simply prevents the contents of those layers from appearing onscreen, which given that the app is in the background should not happen anyway. It removes any system references to cached images. (If your app does not have a strong reference to the images, they are subsequently removed from memory.) It removes strong references to some other system-managed data caches.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. POReducing memory size to ensure backgrounding in iOS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPaul D. Waite
    1. USJonathan
    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. This table or related slice is empty.
    1. COYou can resume this in few words: if you want to have more chances to have the app not killed by iOS while suspended, make it's memory footprint as low as possible. Just to be clear, "reduce strong references" doesn't means that you need to avoid "strong" in the instance variables, you simply need to set to nil as much instance variables as you can before the app goes in background. (so that the memory referenced by that variables has no more strong references --> the memory can be freed)
      singulars
      1. PO
      1. USLombaX
    2. CO(but, see my other comments, this unfortunately doesn't help you :-( )
      singulars
      1. PO
      1. USLombaX
 

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