Once upon a time, Roger Heflin <rogerheflin@xxxxxxxxx> said: > So maybe something similar (update breakage) is happening for chromium also. No, it's not an update vs. existing profile issue, since it happens in mock. I notice that when it happens, I get SELinux denials (which don't happen when it runs okay) for execheap, which appears to be related to mprotect() calls. It's possible that from run to run, the memory layout happens to be a little different, and eventually it's "okay". IIRC there's been kernel changes in that area recently (related to some work being done by Google for Chrome even), so whether this is a Chrome bug (happening due to the kernel tightening the rules) or a kernel bug (being tickled specifically by Chrome)... who knows. -- Chris Adams <linux@xxxxxxxxxxx> -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
