Bug 2309203 - [GCC] firefox-130.0-2.fc40 has issues when showing AVIF images.
Summary: [GCC] firefox-130.0-2.fc40 has issues when showing AVIF images.
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 40
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL: https://yle.fi/news
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-09-02 14:51 UTC by x3x7
Modified: 2025-05-20 19:31 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-05-20 19:31:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Sample image (297.85 KB, image/png)
2024-09-02 15:36 UTC, x3x7
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1916038 0 -- RESOLVED [GCC] Firefox-130.0 has issues when showing AVIF images 2024-09-18 17:17:12 UTC

Description x3x7 2024-09-02 14:51:31 UTC
Using firefox-130.0-2.fc40 load the page from https://yle.fi/news

Images are shown in total black. Expected proper images to be shown.

(loading any .avif image results in display failure) 


Reproducible: Always

Steps to Reproduce:
Load the page from https://yle.fi/news
Actual Results:  
Images are shown in total black.

Expected Results:  
Expected proper images to be shown.

https://bugzilla.mozilla.org/show_bug.cgi?id=1916038

has more details although it is not a Mozilla Firefox issue as version 130.0 binary works properly.

Comment 1 x3x7 2024-09-02 15:36:23 UTC
Created attachment 2045221 [details]
Sample image

Comment 2 x3x7 2024-09-02 17:04:01 UTC
Same problem for firefox-130.0-1.fc42.x86_64.rpm

Comment 3 Martin Stransky 2024-09-03 06:51:22 UTC
Thanks for testing, I see that too. Will look at it.

Comment 4 Martin Stransky 2024-09-03 10:39:00 UTC
Hm, according to log the avif data are decoded correcly...I wonder why we see black space instead.

Comment 5 Martin Stransky 2024-09-03 11:13:23 UTC
Tested upstream nightly with system image libraries but it works as expected.

Comment 6 x3x7 2024-09-03 14:31:42 UTC
Fedora version 129.0.2 does work properly. Initially I thought that version 130.0 uses more patches and that is why the error is triggered. To my surprise version 130 has two fewer patches so something in the existing patch set is triggering the bug with the new 130.0 release.

Since Mozilla’s build works fine I assume removing all patches from the Fedora build would also work fine. This could be tested to make sure the fault is due to source code and not a build problem.

Testing each patch is too time consuming… Maybe somebody with better knowledge of the Firefox code can point out possible triggers for this issue and remove them from the Fedora build.

Comment 7 x3x7 2024-09-03 15:21:11 UTC
Are there some tricks used by the Fedora build to enable multiple CPUs?

Even with spec file update

%global _smp_build_ncpus  6

to restrict the number of active CPUs the firefox build sometimes hangs. Any workaround for this?

Comment 8 x3x7 2024-09-03 16:19:39 UTC
I just tested a build for 130.0 with no patches and the problem is still there. 

Would be nice to know what else is different compared with Mozilla's build configuration. Is that described somewhere on the Net?

Comment 9 Martin Stransky 2024-09-03 19:19:57 UTC
Seems to be caused by GCC build. If I switch to clang it shows the AVIFs correctly.

Comment 10 Martin Stransky 2024-09-03 20:05:21 UTC
Reopened https://bugzilla.mozilla.org/show_bug.cgi?id=1916038 as it's reproducible on latest trunk with GCC too.

Comment 11 Aoife Moloney 2025-04-28 13:43:22 UTC
This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 12 Aoife Moloney 2025-05-20 19:31:40 UTC
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13.

Fedora Linux 40 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.