Bug 177406 – Images may render partial frames even after loading all the encoded data

• Status: RESOLVED
• Resolution: FIXED
• Component: Images

[Said Abou-Hallawa]

This bug can happen if the image decoding thread is closed after it finished decoding the partially loaded frame. The dead decoding thread can shuts down itself if the SynchronizedFixedQueue notifies it that it has been closed. This can happen if the dispatcher makes this thread active. But before this happens, new image data is received, the image renderer is invalidated and a new decoding request is made. So a new decoding thread is created and a frame request is pushed to the SynchronizedFixedQueue. The dead thread still can access the SynchronizedFixedQueue but it did not get a chance to be active between closing the SynchronizedFixedQueue and reopening it. So the dead thread dequeues the new decoding request. When it finishes decoding, it realizes it is already dead so it drops the decoded frame. So although we received new image data we do not draw a newer image frame. If this happens after receiving all the data, the full image full won't be rendered.

This is the calling stack that can lead to this bug:

// Receiving image data and render repaint.
BitmapImage::draw()
ImageSource::requestFrameAsyncDecodingAtIndex()
ImageFrameCache::requestFrameAsyncDecodingAtIndex()
ImageFrameCache::startAsyncDecodingQueue()
WorkQueue::create()                                 // Creates a WorkQueue, say WQ1.
  ImageDecoder::createFrameImageAtIndex()           // Happens in the decoding thread WQ1.
  callOnMainThread()                                // Gets dispatched from WQ1.
    ImageFrameCache::cacheNativeImageAtIndexAsync() // Get called from callOnMainThread() from the decoding thread WQ1.
    BitmapImage::imageFrameAvailableAtIndex()       // The renderer is invalidated
    ImageSource::stopAsyncDecodingQueue()
    ImageFrameCache::stopAsyncDecodingQueue()
    SynchronizedFixedQueue::close()
BitmapImage::draw()                                 // The new frame is drawn.

// Receiving image data and render repaint.
BitmapImage::draw()
ImageSource::requestFrameAsyncDecodingAtIndex()
ImageFrameCache::requestFrameAsyncDecodingAtIndex()
ImageFrameCache::startAsyncDecodingQueue()
WorkQueue::create()                                 // Creates a WorkQueue, say WQ2
  ImageDecoder::createFrameImageAtIndex()           // Happens in the dead decoding thread WQ1
  callOnMainThread()                                // Gets dispatched from WQ1.
     m_decodingQueue != protectedQueue              // This frame is dropped to the floor and the render does not get repainted.

[Said Abou-Hallawa]

Created attachment 321622 [details]
Patch

[Said Abou-Hallawa]

<rdar://problem/34588529>

[Simon Fraser (smfr)]

Comment on attachment 321622 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=321622&action=review

> Source/WTF/wtf/SynchronizedFixedQueue.h:43
>      SynchronizedFixedQueue()

This constructor should be private now.

> Source/WebCore/platform/graphics/ImageFrameCache.cpp:327
> +    ASSERT(m_frameRequestQueue);
> +    m_frameRequestQueue->enqueue({ index, subsamplingLevel, sizeForDrawing, decodingStatus });

The ASSERT is pointless because you'll crash on the next line anyway.

[Said Abou-Hallawa]

Created attachment 321636 [details]
Patch

[Said Abou-Hallawa]

Comment on attachment 321622 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=321622&action=review

>> Source/WTF/wtf/SynchronizedFixedQueue.h:43
>>      SynchronizedFixedQueue()
> 
> This constructor should be private now.

This wil require changing TestWebKitAPI/Tests/WTF/SynchronizedFixedQueue.cpp. And I wanted to make the smallest change to fix this bug.

>> Source/WebCore/platform/graphics/ImageFrameCache.cpp:327
>> +    m_frameRequestQueue->enqueue({ index, subsamplingLevel, sizeForDrawing, decodingStatus });
> 
> The ASSERT is pointless because you'll crash on the next line anyway.

Done. And it should not be null since ImageFrameCache::requestFrameAsyncDecodingAtIndex() ensures the decoding thread is created by calling ImageFrameCache::startAsyncDecodingQueue(). This function calls ImageFrameCache::frameRequestQueue() which ensures the m_frameRequestQueue is created.

[Simon Fraser (smfr)]

(In reply to Said Abou-Hallawa from comment #5)
> Comment on attachment 321622 [details]
> Patch
> 
> View in context:
> https://bugs.webkit.org/attachment.cgi?id=321622&action=review
> 
> >> Source/WTF/wtf/SynchronizedFixedQueue.h:43
> >>      SynchronizedFixedQueue()
> > 
> > This constructor should be private now.
> 
> This wil require changing
> TestWebKitAPI/Tests/WTF/SynchronizedFixedQueue.cpp. And I wanted to make the
> smallest change to fix this bug.

Then you should change the test. The way it is, someone can make a SynchronizedFixedQueue on the stack which makes no sense for a ref-counted object (and is dangerous).

[WebKit Commit Bot]

The commit-queue encountered the following flaky tests while processing attachment 321636 [details]:

http/tests/security/cross-origin-xsl-BLOCKED.html bug 51054 (authors: [e-mail], [e-mail], and [e-mail])
The commit-queue is continuing to process your patch.

[WebKit Commit Bot]

Comment on attachment 321636 [details]
Patch

Clearing flags on attachment: 321636

Committed r222427: <http://trac.webkit.org/changeset/222427>

[WebKit Commit Bot]

All reviewed patches have been landed.  Closing bug.

[Darin Adler]

Comment on attachment 321636 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=321636&action=review

> Source/WebCore/platform/graphics/ImageFrameCache.h:142
>      Ref<WorkQueue> decodingQueue();

This likely should just return WorkQueue&, not Ref<WorkQueue>, unless there is some case where this creates a newly created queue or there is some major risk of it being deallocated while being used.

> Source/WebCore/platform/graphics/ImageFrameCache.h:143
> +    Ref<SynchronizedFixedQueue<ImageFrameRequest, BufferSize>> frameRequestQueue();

I think this should return just a plain reference, not a Ref<>, for the same reasons I cited above.

[Said Abou-Hallawa]

The followup bug is https://bugs.webkit.org/show_bug.cgi?id=177458