loading an image top level can often lead to two decodes of it
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
People
(Reporter: mayankleoboy1, Unassigned)
References
()
Details
Download the 63.9MB image file from https://drive.google.com/drive/folders/14PJk9qa9pT0IDNulJMNGRmVWDQLsLm7r
Open it in Firefox.
AR: https://share.firefox.dev/3Rf7mjy
The profile suggests two taskcontroller threads used to decode the image. Consider increasing the number of threads.
I can imagine this being a low priority enhancement as most images on the web are probably served well with 2 threads.
tnikkel: Feel free to resolve WONTFIX :)
| Reporter | ||
Comment 1•1 year ago
•
|
||
For comparison, Chrome doesnt open the image at all.
And native Windows11 image viewer application opens this image instantanously.
Comment 2•1 year ago
|
||
We don't split a single decode of an image over more than 1 thread. So what you are seeing are two different decodes of the same image. If we had more images we would use more threads. The fact that we are seeing two decodes of the image though is worth investigating. Normally two identical decodes should not happen, so either there is a bug, or there is some difference in the decode request, the most common difference would be the output size differs (we support downscaled decodes).
Comment 3•1 year ago
|
||
I can reproduce the two decodes in my main profile, but I can't reproduce in a fresh profile or another profile I have around that's a little less fresh. I wonder what are steps that would reproduce the two decodes?
Comment 4•1 year ago
|
||
I'm gonna morph this.
Comment 5•1 year ago
|
||
The severity field is not set for this bug.
:tnikkel, could you have a look please?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
| Reporter | ||
Comment 6•1 year ago
|
||
The situation is wonkier. I have a large 330MB png file and a 180MB jpeg file.
When i drag-and-drop the image from local machine to a fresh browser, strange things happen :
2 TC threads: https://share.firefox.dev/3CephCD
1 TC thread: https://share.firefox.dev/3E1oSnz
Decoding on MT + 1 TC thread , and 1TC of another process: https://share.firefox.dev/4jb3jBi (Here, only 1 tab is open but profiler shows 2 fileinputs!!)
3 TC threads + 2TC threads: https://share.firefox.dev/3C87OMj (open image in window and then maximize window)
Description
•