Setting -fwrapv in cflags makes signed integer overflow defined behavior, improving memory safety. Without this setting, signed integer overflow is undefined behavior. This leads compilers to do surprising things like "optimizing out" explicit overflow checks that happen too late or themselves overflow. Sometimes these overflow checks are needed for memory safety. Other chromium distributions already apply this patch for this reason: https://github.com/GrapheneOS/Vanadium/blob/main/patches/0004-enable-fwrapv-in-Clang-for-non-UBSan-builds.patch It is not at all clear why upstream doesn't already do this: https://issues.chromium.org/issues/40164442 Reproducible: Always
FEDORA-2024-ef56ea86fc (chromium-122.0.6261.69-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ef56ea86fc
FEDORA-2024-ef56ea86fc has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ef56ea86fc` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ef56ea86fc See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2024-ef56ea86fc (chromium-122.0.6261.69-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report.