Databases
StackOverflow2013
Postsdbo
POBitmapFactory.Options.inBitmap causes tearing when switching ImageView bitmap often
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POBitmapFactory.Options.inBitmap causes tearing when switching ImageView bitmap often
    primarykey
    data
    text
    <p>I've encountered a situation where I have to display images in a slideshow that switches image very fast. The sheer number of images makes me want to store the JPEG data in memory and decode them when I want to display them. To ease on the Garbage Collector, I'm using <a href="http://developer.android.com/reference/android/graphics/BitmapFactory.Options.html#inBitmap" rel="noreferrer">BitmapFactory.Options.inBitmap</a> to reuse bitmaps.</p> <p>Unfortunately, this causes rather severe tearing, I've tried different solutions such as synchronization, semaphores, alternating between 2-3 bitmaps, however, none seem to fix the problem.</p> <p>I've set up an example project which demonstrates this issue over at GitHub; <a href="https://github.com/Berglund/android-tearing-example" rel="noreferrer">https://github.com/Berglund/android-tearing-example</a></p> <p>I've got a thread which decodes the bitmap, sets it on the UI thread, and sleeps for 5 ms:</p> <pre><code>Runnable runnable = new Runnable() { @Override public void run() { while(true) { BitmapFactory.Options options = new BitmapFactory.Options(); options.inSampleSize = 1; if(bitmap != null) { options.inBitmap = bitmap; } bitmap = BitmapFactory.decodeResource(getResources(), images.get(position), options); runOnUiThread(new Runnable() { @Override public void run() { imageView.setImageBitmap(bitmap); } }); try { Thread.sleep(5); } catch (InterruptedException e) {} position++; if(position &gt;= images.size()) position = 0; } } }; Thread t = new Thread(runnable); t.start(); </code></pre> <p>My idea is that ImageView.setImageBitmap(Bitmap) draws the bitmap on the next vsync, however, we're probably already decoding the next bitmap when this happens, and as such, we've started modifying the bitmap pixels. Am I thinking in the right direction?</p> <p>Has anyone got any tips on where to go from here?</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCharles
    1. USJoakim Berglund
    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. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POBitmapFactory.Options.inBitmap causes tearing when switching ImageView bitmap often
      1. USJoakim Berglund
      1. VTFavorite
    2. VO
      singulars
      1. POBitmapFactory.Options.inBitmap causes tearing when switching ImageView bitmap often
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POBitmapFactory.Options.inBitmap causes tearing when switching ImageView bitmap often
      1. USJoakim Berglund
      1. VTBountyStart
    1. COIs `ImageView` a necessary requirement ? I'd suggest `SurfaceView` or `TextureView` for high draw rates.
      singulars
      1. POBitmapFactory.Options.inBitmap causes tearing when switching ImageView bitmap often
      1. USS.D.
 

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