There's a couple of issues here:
- The new glibc defines MADV_FREE which Chromium detects at compile-time and
results in a runtime dependency on it. However, this was only added to linux
4.5.
- The seccomp sandbox doesn't allow madvise(MADV_FREE), which is likely what
this crash is.
** Changed in: glibc (Ubuntu)
Status: Invalid => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1613258
Title:
signal 4 ILL_ILLOPN in webbrowser-app tests (glibc upgrade?)
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1613258/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
