[Bug 1613258] Re: signal 4 ILL_ILLOPN in webbrowser-app tests (glibc upgrade?)

[Chris Coulson]

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
Foundations Bugs, which is subscribed to glibc in Ubuntu.
https://bugs.launchpad.net/bugs/1613258

Title:
  signal 4 ILL_ILLOPN in webbrowser-app tests (glibc upgrade?)

Status in Oxide:
  Triaged
Status in Oxide 1.16 series:
  New
Status in Oxide 1.17 series:
  New
Status in glibc package in Ubuntu:
  Triaged

Bug description:
  This is happening with a no-change rebuild of webbrowser-app, with the
  most likely candidate for the problem trigger being the new glibc 2.24
  in yakkety-proposed.

  ---
  https://launchpadlibrarian.net/279047362/buildlog_ubuntu-yakkety-i386.webbrowser-app_0.23+16.10.20160803.1-0ubuntu2_BUILDING.txt.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1613258/+subscriptions