Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It looks like there should only be one bitmap in memory at a time. A few thoughts.</p> <p>First when recycling the bitmap set it to null, also set the canvas to null. If this does not solve the issue, i would be curious to see the code you are using to actually paint the lines. Also getting a heap dump after invoking the dialog and closing it will show you which objects are still in memory, and allow you to quickly track down what is holding on to the bitmap, and it's kinda fun :)</p> <p>This <a href="http://android-developers.blogspot.com/2011/03/memory-analysis-for-android.html" rel="nofollow">post</a> is a great start on investigating a heap dump if you have not done it before.</p> <p>UPDATE</p> <p>To set the canvas to null, you can do something like this</p> <pre><code>public void recycling() { bitmap.recycle(); bitmap = null; bitmapCanvas = null; } </code></pre> <p>However upon closer inspection of your code, i see that you are creating a new dialog everytime and then dismissing the dialog. This will not free up the dialog from memory. Try updating your code so you only initialize the dialog if it is null.</p> <pre><code>public void write_board () { if(writing_dialog == null){ writing_dialog = new Dialog(Apple.this, android.R.style.Theme_Translucent_NoTitleBar); WindowManager.LayoutParams lp = writing_dialog.getWindow().getAttributes(); lp.dimAmount = 0.5f; writing_dialog.getWindow().addFlags(WindowManager.LayoutParams.FLAG_DIM_BEHIND); Window window = writing_dialog.getWindow(); window.setGravity(Gravity.CENTER); writing_dialog.setContentView(R.layout.alert_drawing_pad); writing_dialog.setCancelable(true); writing_dialog.setVolumeControlStream(AudioManager.STREAM_MUSIC); } //now do stuff with your dialog writing_dialog.show(); doodleView = (DoodleView) writing_dialog.findViewById(R.id.doodleView); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POAndroid: free up bitmap memory resources programmatically
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USbroschb
    1. USbroschb
    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. COhow to set the canvas to null?
      singulars
      1. PO
      1. USpearmak
    2. CO@pearmak see my updated answer
      singulars
      1. PO
      1. USbroschb
    3. COmany thanks! I have just tried your suggested updates by adding `bitmapCanvas = null`, it is now performing better, in a way that it still triggers the less serious `E/OpenGLRenderer(25296): Out of memory!` but will not trigger fatal `java.lang.OutOfMemoryError`...yet for further information, actually besides apple class, for example, I have some more classes (eg, apple, banana, cake) that also pops up a writing board. within the same class, it will not trigger `out of memory` but running across class A then B then C till K it will trigger...the dialog should have recycled across activities?
      singulars
      1. PO
      1. USpearmak
 

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