Open Bug 983051 Opened 10 years ago Updated 2 years ago

Decode on draw sometimes decode too early

Categories

(Core :: Graphics: ImageLib, defect, P3)

All
Gonk (Firefox OS)
defect

Tracking

()

People

(Reporter: kanru, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: perf, Whiteboard: [c=memory p= s= u=tarako] [MemShrink:P2][demo])

+++ This bug was initially created as a clone of Bug #945161 +++

Even image.mem.decodeondraw is true we sometimes still decode the full image when all data is available. It happens when the image is in cache and downloads very fast.
What causes the full decode?
Depends on: 983056
(In reply to Timothy Nikkel (:tn) from comment #1)
> What causes the full decode?

I'm not sure. I could be wrong. There seems so many way to trigger decode but some look suspicious. For example this one:

 http://hg.mozilla.org/mozilla-central/file/46041cc216fd/image/src/RasterImage.cpp#l1663

And this one:

 http://hg.mozilla.org/mozilla-central/file/46041cc216fd/image/src/RasterImage.cpp#l1739

For bug 945161 we want to get the layout information before we fully decode the image. But sometimes I couldn't get the frame size before we start decoding.
Depends on: 984759
No longer depends on: 984759
Depends on: ddd
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.