IIUC only yakkety on kernel 4.4 was affected. yakkety now has kernel 4.8
so it should be fine regardless, and Cr 57 should have fixed the issue
anyway. I’m tentatively marking the bug fixed, feel free to re-open if
needed.
** Changed in: chromium-browser (Ubuntu)
Status: Confirmed => Fix
I'm running 57.0.2987.98-0ubuntu1.1348 on Zesty without this error.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage notifications about this bug
This was fixed upstream with
https://chromium.googlesource.com/chromium/src/+/65180d3bfbec6fb3d0ed2ca7961094fb38452832,
which presumably shipped in Cr 57.
@nick-moffitt: is this crash still affecting you?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Due to suspend/resume+wifi driver issues, I can't upgrade the kernel.
Downgrading Chromium works around this problem (though not very pretty).
The previous version is still available here
https://launchpad.net/ubuntu/+source/chromium-
browser/55.0.2883.87-0ubuntu2.1329/+build/12052688
--
You
Confirmed. Updating to 4.8 (from 4.4) fixed the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage notifications about this bug go to:
Joachim Haga seems to be correct. I ran earlier 4.4 kernel (for
unrelated stability problems) but now that I try with 4.8, newest
Chromium works.
$ uname -a
Linux ovidius 4.8.0-41-generic #44-Ubuntu SMP Fri Mar 3 15:26:20 UTC 2017 i686
i686 i686 GNU/Linux
$ chromium-browser --version
Using
Same here. I am using kernel 4.4 (linux-lts-xenial). Did anyone try it
with > 4.4?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage notifications
FWIW:
The stacktrace looks very similar to this one:
https://github.com/saiarcot895/chromium-ubuntu-build/issues/5
...which was apparently caused by attempting to use MADV_FREE (which was
added in kernel 4.5) on 4.4.
** Bug watch added: github.com/saiarcot895/chromium-ubuntu-build/issues #5
Well that's highly fortunate for you, Max, but mine's still utterly
unusable!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage notifications
I don't know why, but all of a sudden, chromium is working for me again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage notifications about
Isn't this almost a security risk since people will be using older
versions that work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage
** Changed in: chromium-browser (Ubuntu)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage notifications
wieczyk, where did you get the older deb? I am struggling to get back
to a chromium that works!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage
Something similar here.
The chromium-browser_55.0.2883.75-0ubuntu0.16.10.1327_amd64.deb works.
Received signal 4 ILL_ILLOPN 7f8bd71d19e7
#0 0x7f8bf481500e base::debug::StackTrace::StackTrace()
#1 0x7f8bf4815403
#2 0x7f8bf4b2a630
#3 0x7f8bd71d19e7 WTF::decommitSystemPages()
#4 0x7f8be37197b0
After the latest update getting stack traces and "aw snap" pages after
every time a tab accesses anything, even Chromium settings page.
Received signal 4 ILL_ILLOPN af84a7f4
#0 0xb75a0e04 base::debug::StackTrace::StackTrace()
#1 0xb75a12d7
#2 0xb7707c20 ([vdso]+0xc1f)
#3
Where did you install that from?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage notifications about this bug go to:
For what it's worth, using Google Chrome 56.0.2924.87 freshly installed
works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Received signal 4 ILL_ILLOPN
To manage
Me too. I downgraded to release version 53.0.2785.143 and chromium works
again. However, now I can't access any password and
chrome:settings/passwords shows empty. Does anyone know how I can get my
passwords back in chromium?
--
You received this bug notification because you are a member of
Lest anyone blame my configuration, this also occurs when I run it like
so:
/usr/bin/chromium-browser --user-data-dir=$(mktemp -d)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
Title:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1669344
20 matches
Mail list logo
