ubuntu-webapps-bugs team mailing list archive

Thread
Date

[Bug 1613258] Re: Web browser can't browse anything - "The rendering process has been closed for this tab" [signal 4 ILL_ILLOPN]

To: ubuntu-webapps-bugs@xxxxxxxxxxxxxxxxxxx
From: Chris Coulson <chrisccoulson@xxxxxxxxxx>
Date: Tue, 23 Aug 2016 11:18:08 -0000
Reply-to: Bug 1613258 <1613258@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Marking the glibc task as invalid (see IRC conversation)

<chrisccoulson> does the kernel in yakkety support MADV_FREE?
<apw> chrisccoulson, that is documented as 4.5+ so we will, and currently don't
<chrisccoulson> apw, ah thanks. See bug 1613258 for context - the new glibc defines MADV_FREE
<apw> chrisccoulson, that may have been built with the 4.6 which was in -proposed for a time (glibc)
<apw> that said, i am supprised that glibc is assuming it can use it
 infinity, ^
<apw> chrisccoulson, oh but it is likely the seccomp bits right?  so just a profile change ?
 chrisccoulson, in the sense it is resonable for glibc to define it, and the kernel to return EINVAL or indeed work, but we need the seccomp profile to reflect that possibility
<chrisccoulson> apw, we'll probably end up doing the same as http://code.qt.io/cgit/qt/qtwebengine-chromium.git/commit/?h=49-based&id=b12ffcd411d4776f7120ccecb3be34344d930d2b
<apw> chrisccoulson, wouldn't it make more sense to try MADV_FREE and if it fails ENOSUPPORT or whatever dropback to whatever it does when it doesn't have _FREE ?
<apw> so one uses it in 4.5 and not before that all shiney and automatically 
<chrisccoulson> apw, we could probably do that

** Changed in: glibc (Ubuntu)
       Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
WebApps bug tracking, which is subscribed to Oxide.
https://bugs.launchpad.net/bugs/1613258

Title:
  Web browser can't browse anything - "The rendering process has been
  closed for this tab" [signal 4 ILL_ILLOPN]

Status in Canonical System Image:
  New
Status in Oxide:
  Fix Committed
Status in Oxide 1.16 series:
  Triaged
Status in Oxide 1.17 series:
  Fix Committed
Status in glibc package in Ubuntu:
  Invalid

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/canonical-devices-system-image/+bug/1613258/+subscriptions