Closed Bug 905793 Opened 9 years ago Closed 9 years ago
Frame::m Decoded could be out of date, rendering img Frame::Image Complete() to be wrong
imgFrame::mDecoded appears to only be updated in imgFrame::ImageUpdated, which is in turn only called from Decoder::PostInvalidation(), which is only mean for mid frame calls. So, mDecoded ends up being wrong for images that decode completely and only go through Decoder::PostFrameStop. For those cases, imgFrame::ImageComplete() result will be wrong. This was the underlying cause for bug 899861 - we were testing if the frames in the image sequence were "ImageComplete" and they never were, because each frame in the sequence would decode fast enough. The problem doesn't seem to be limited to image sequences, but in other scenarios the decoding is done when the image is done, so we do the right thing because the decoding is completed.
9 years ago
FlushImageData() also doesn't get called beyond the first frame, so we don't think any frames are "ImageComplete" until the very end. Seth, does the above make sense, or am I reading the code wrong?
I can't tell if this is an overkill and we should do this update elsewhere, or in fewer cases.
Comment on attachment 790951 [details] [diff] [review] Send ImageUpdated() in PostFrameStop(). Review of attachment 790951 [details] [diff] [review]: ----------------------------------------------------------------- As far as I can tell, this is OK. The worst consequence seems to be that you take mDirtyMutex an extra time on the first frame. (Which seems inevitable.)
Attachment #790951 - Flags: review?(seth) → review+
Comment on attachment 790951 [details] [diff] [review] Send ImageUpdated() in PostFrameStop(). Jeff's good with Seth's review, taking him off the review?
9 years ago
Assignee: nobody → milan
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in before you can comment on or make changes to this bug.