Bug 1569724 Comment 9 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Hiroyuki Ikezoe (:hiro) from comment #6)
> Confirmed that [the revision right before bug 1436058](https://hg.mozilla.org/mozilla-central/rev/9bc3906d3dc9535d26c4d172df8457d853b86d2b) doesn't have the issue and [the last commit of bug 1436058](https://hg.mozilla.org/mozilla-central/rev/f53e340b051cec79c3dab594fe87e8e805ba2fab) has the issue.

The above was related to a root cause. AsyncImagePipelineManager::UpdateImageKeys() requests to use different TextureHost for updating rendering. And PersistentBufferProviderShared does not work well with AsyncImagePipelineManager: and WR in the user case.
Revision 1 by
on 
(In reply to Hiroyuki Ikezoe (:hiro) from comment #6)
> Confirmed that [the revision right before bug 1436058](https://hg.mozilla.org/mozilla-central/rev/9bc3906d3dc9535d26c4d172df8457d853b86d2b) doesn't have the issue and [the last commit of bug 1436058](https://hg.mozilla.org/mozilla-central/rev/f53e340b051cec79c3dab594fe87e8e805ba2fab) has the issue.

The above was related to a root cause. AsyncImagePipelineManager::UpdateImageKeys() requests to use different TextureHost for updating rendering. And PersistentBufferProviderShared does not work well with AsyncImagePipelineManager and WR in the user case.

Back to Bug 1569724 Comment 9