Fix stack smash crashes on Linux #493
No reviewers
Labels
No labels
area/accessibility
area/dependency
Confirmed
Crash Report
Delayed
Design Issue
Duplicate
Feedback required
Good first issue
kind/bug
kind/cleanup
kind/enhancement
platform/linux
platform/macos
platform/windows
priority/high
Question
Request for Comments
Seeking Other Contributors
Seeking Testers
Won't Fix / By Design
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-obsproject/obs-browser!493
Loading…
Reference in a new issue
No description provided.
Delete branch "fix-stack-smash-crashes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Description
See: https://github.com/chromiumembedded/cef/issues/3912
Fedora bug: https://bugzilla.redhat.com/show_bug.cgi?id=2379591
How Has This Been Tested?
Local test build
Types of changes
Checklist:
cc @tytan652 @GeorgesStavracas
Is this fixing an issue currently in the wild? Want to gauge whether this needs to land in a 31.1.x release or if it can wait until a future major/minor release.
It's not exclusive to 31.1 (earlier version have the issue) and will require to backport changes to CEF 127 to have
NO_STACK_PROTECTORdefined and enable the decoration.So in my opinion it can wait until a future major/minor release.
The main issue is noise for distros that have coredumps/reporting (like Fedora). Other than that it seems to be harmless since the crashes only happen on process exit.
For the fedora RPMs I will push this patch in so it's fixed there, since otherwise users will get abrt popups and file bugs with us (I already got one). I can't say about the effect for other distros or through the official Flatpak. If this has been going on for a while and nobody has complained about it yet, maybe it's fine to wait?