Ubuntu
chromium-browser package

chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

Bug #1702501 reported by Rohan Bayer-Fox

This bug report was converted into a question: question #646254: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010.

54
This bug affects 12 people
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

After I updated Chromium to the latest version today, it crashed as soon as executed. When executed from a terminal, I got:

Received signal 11 SEGV_MAPERR 000000000010
#0 0x7f5c4b92d425 base::debug::StackTrace::StackTrace()
#1 0x7f5c4b92d80b <unknown>
#2 0x7f5c4bc58390 <unknown>
#3 0x55ae23b43dc8 <unknown>
#4 0x55ae23b46656 <unknown>
#5 0x55ae23b46df9 <unknown>
#6 0x55ae23b47143 <unknown>
#7 0x7f5c4b9a8821 <unknown>
#8 0x7f5c4b92eeea base::debug::TaskAnnotator::RunTask()
#9 0x7f5c4b957e90 base::MessageLoop::RunTask()
#10 0x7f5c4b95997d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7f5c4b95a83d <unknown>
#12 0x7f5c4b95b300 base::MessagePumpLibevent::Run()
#13 0x7f5c4b956f15 base::MessageLoop::RunHandler()
#14 0x7f5c4b981628 base::RunLoop::Run()
#15 0x7f5c4b9ade36 base::Thread::ThreadMain()
#16 0x7f5c4b9a8726 <unknown>
#17 0x7f5c4bc4e6ba start_thread
#18 0x7f5c352fd3dd clone
  r8: 000000000000002e r9: 000055ae2559a6ec r10: 0000000000000000 r11: 00007f5c3538af50
 r12: 00007f5bc6b2aff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f5bc6b2aeb0
  di: 0000000000000000 si: 00007f5bc6b2aeb0 bp: 00007f5bc6b2af00 bx: 00007f5bc6b2aeb0
  dx: 0000000000000067 ax: 0000000000000000 cx: 00007f5bdc1079c0 sp: 00007f5bc6b2ae60
  ip: 000055ae23b43dc8 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

I tried complete reinstallation, purged and removed .config/chromium. Same problem. When I restored .config/chromium from an earlier working version, it crashed with:

[8159:8202:0705/102433.905625:ERROR:service_manager.cc(158)] Connection InterfaceProviderSpec prevented service: content_plugin from binding interface: memory_instrumentation::mojom::Coordinator exposed by: content_browser
A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
A Parser-blocking, cross site (i.e. different eTLD+1) script, https://ssl.google-analytics.com/ga.js, is invoked via document.write. The network request for this script MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.
Received signal 11 SEGV_MAPERR 000000000010
#0 0x7f3a02096425 base::debug::StackTrace::StackTrace()
#1 0x7f3a0209680b <unknown>
#2 0x7f3a023c1390 <unknown>
#3 0x5604c6bcadc8 <unknown>
#4 0x5604c6bcd656 <unknown>
#5 0x5604c6bcddf9 <unknown>
#6 0x5604c6bce143 <unknown>
#7 0x7f3a02111821 <unknown>
#8 0x7f3a02097eea base::debug::TaskAnnotator::RunTask()
#9 0x7f3a020c0e90 base::MessageLoop::RunTask()
#10 0x7f3a020c297d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7f3a020c383d <unknown>
#12 0x7f3a020c4300 base::MessagePumpLibevent::Run()
#13 0x7f3a020bff15 base::MessageLoop::RunHandler()
#14 0x7f3a020ea628 base::RunLoop::Run()
#15 0x7f3a02116e36 base::Thread::ThreadMain()
#16 0x7f3a02111726 <unknown>
#17 0x7f3a023b76ba start_thread
#18 0x7f39eba663dd clone
  r8: 000000000000002e r9: 00005604c86216ec r10: 0000000000000000 r11: 00007f39ebaf3f50
 r12: 00007f39748cbff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f39748cbeb0
  di: 0000000000000000 si: 00007f39748cbeb0 bp: 00007f39748cbf00 bx: 00007f39748cbeb0
  dx: 0000000000000067 ax: 0000000000000000 cx: 00007f39d003a050 sp: 00007f39748cbe60
  ip: 00005604c6bcadc8 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

When I open Chromium with a temporary profile, the window opens, but as soon as I enter "No thanks" to the option of signing in with Google, it crashes as above.

Revision history for this message
Rohan Bayer-Fox (rbayerfox) wrote :

I cannot believe I am the only one to experience this bug. Is there anything I should try which I have not yet tried?

Changed in chromium-browser (Ubuntu):
status: New → Invalid
Revision history for this message
actionparsnip (andrew-woodhead666) wrote :

What is the output of:

lsb_release -a; uname -a; apt-cache policy chromium-browser

Thanks

Revision history for this message
Rohan Bayer-Fox (rbayerfox) wrote : Re: [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
Linux rohan-T500 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
chromium-browser:
  Installed: 59.0.3071.109-0ubuntu0.16.04.1289
  Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
  Version table:
 *** 59.0.3071.109-0ubuntu0.16.04.1289 500
        500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     49.0.2623.108-0ubuntu1.1233 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

---------- Original Message ----------
From: actionparsnip <email address hidden>
To: <email address hidden>
Subject: [Bug 1702501] Re: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
Date: Wed, 05 Jul 2017 15:47:39 -0000

What is the output of:

lsb_release -a; uname -a; apt-cache policy chromium-browser

Thanks

--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1702501

Title:
  chromium-browser crashes soon after execution - Received signal 11
  SEGV_MAPERR 000000000010

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1702501/+subscriptions
____________________________________________________________
Actress Reveals Hollywood Secret “Flattening� Bloated Belly
ActivatedYou
http://thirdpartyoffers.juno.com/TGL3131/595d29a22fbfc29a23cbest02vuc

Revision history for this message
Fabian Tröster (fabian-troester) wrote :

Hi, I get the absolute exact same error messages when starting chromium (to the last letter) since the last chromium update (to Version 59.0.3071.109), which is why you should still consider that to be a bug!
I tried downgrading and got a ton of error messages from apt, so I let that be. I am really quite disappointed that those updates are not tested properly.

so ... lsb_release:
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:core-4.1-amd64:core-4.1-noarch

uname -a:
Linux <yes there's a name> 4.4.0-85-generic #108-Ubuntu SMP Mon Jul 3 17:23:59 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

apt-cache policy chromium-browser:
chromium-browser:
  Installiert: 59.0.3071.109-0ubuntu0.16.04.1289
  Installationskandidat: 59.0.3071.109-0ubuntu0.16.04.1289
  Versionstabelle:
 *** 59.0.3071.109-0ubuntu0.16.04.1289 500
        500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     49.0.2623.108-0ubuntu1.1233 500
        500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

I would strongly suggest, you treat that as a bug! I know it is a lot easier to say: "Oo, you know, it is your own fault." No, it is a bug. It was working before the update and after the last update it stopped working. That's a bug.

Changed in chromium-browser (Ubuntu):
status: Invalid → New
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in chromium-browser (Ubuntu):
status: New → Confirmed
Revision history for this message
Dave Nicolai (dacurnico) wrote :

I'm getting the same error here, started this morning after update. OS was a recent install of Mint Cinnamon 18.2 with Oibaf graphics PPA and some theming, so I re-installed to ensure it wasn't due to my changes. Same error on a totally stock, fresh install.

As reported by OP, deleting Chromium config (mv /home/user/.config/chromium /home/user/.config/chromium.bak) allows the browser to run once but will crash after skipping Google login.

Hardware: Dell XPS 15 9530 (i7-4702HQ, Haswell)

As requested above:
lsb_release -a; uname -a; apt-cache policy chromium-browser

No LSB modules are available.
Distributor ID: LinuxMint
Description: Linux Mint 18.2 Sonya
Release: 18.2
Codename: sonya
Linux graphite 4.8.0-53-generic #56~16.04.1-Ubuntu SMP Tue May 16 01:18:56 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
chromium-browser:
  Installed: 59.0.3071.109-0ubuntu0.16.04.1289
  Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
  Version table:
 *** 59.0.3071.109-0ubuntu0.16.04.1289 500
        500 http://mirrors.us.kernel.org/ubuntu xenial-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     49.0.2623.108-0ubuntu1.1233 500
        500 http://mirrors.us.kernel.org/ubuntu xenial/universe amd64 Packages

Revision history for this message
Bruno (bhenrique) wrote :

Same here, started a few hours ago.

Hardware: Dell Latitude 5470 (i7-6820HQ)

lsb_release -a; uname -a; apt-cache policy chromium-browser

LSB Version: core-9.20160110ubuntu5-amd64:core-9.20160110ubuntu5-noarch:security-9.20160110ubuntu5-amd64:security-9.20160110ubuntu5-noarch
Distributor ID: Ubuntu
Description: Ubuntu 16.10
Release: 16.10
Codename: yakkety
Linux brhenrique-Latitude-E5470 4.8.0-58-generic #63-Ubuntu SMP Mon Jun 26 17:08:21 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
chromium-browser:
  Installed: 59.0.3071.109-0ubuntu0.16.10.1357
  Candidate: 59.0.3071.109-0ubuntu0.16.10.1357
  Version table:
 *** 59.0.3071.109-0ubuntu0.16.10.1357 500
        500 http://br.archive.ubuntu.com/ubuntu yakkety-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu yakkety-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     53.0.2785.143-0ubuntu1.1307 500
        500 http://br.archive.ubuntu.com/ubuntu yakkety/universe amd64 Packages

Revision history for this message
Bernhard Zürn (bernhard-zuern) wrote :

same here since last ap-get upgrade on xenial

$ chromium-browser
Received signal 11 SEGV_MAPERR 000000000010
#0 0x7f0a6a4d6425 base::debug::StackTrace::StackTrace()
#1 0x7f0a6a4d680b <unknown>
#2 0x7f0a6a801390 <unknown>
#3 0x558b2b4b8dc8 <unknown>
#4 0x558b2b4bb656 <unknown>
#5 0x558b2b4bbdf9 <unknown>
#6 0x558b2b4bc143 <unknown>
#7 0x7f0a6a551821 <unknown>
#8 0x7f0a6a4d7eea base::debug::TaskAnnotator::RunTask()
#9 0x7f0a6a500e90 base::MessageLoop::RunTask()
#10 0x7f0a6a50297d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7f0a6a50383d <unknown>
#12 0x7f0a6a504300 base::MessagePumpLibevent::Run()
#13 0x7f0a6a4fff15 base::MessageLoop::RunHandler()
#14 0x7f0a6a52a628 base::RunLoop::Run()
#15 0x7f0a6a556e36 base::Thread::ThreadMain()
#16 0x7f0a6a551726 <unknown>
#17 0x7f0a6a7f76ba start_thread
#18 0x7f0a53e883dd clone
  r8: 000000000000002e r9: 0000558b2cf0f6ec r10: 0000000000000000 r11: 00007f0a53f15f50
 r12: 00007f09d5c10ff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f09d5c10eb0
  di: 0000000000000000 si: 00007f09d5c10eb0 bp: 00007f09d5c10f00 bx: 00007f09d5c10eb0
  dx: 0000000000000061 ax: 0000000000000000 cx: 00007f098c008aa0 sp: 00007f09d5c10e60
  ip: 0000558b2b4b8dc8 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Dell XPS Core i7

Revision history for this message
Sam M (sam-samuel-magnan) wrote :

Well I just got the same error. How it happens is a little bit different. I was browsing since around 2 hours with no issue, after boot. Then suddenly a few websites became laggy and then crash... Trying to restart it gave me the same error

Received signal 11 SEGV_MAPERR 000000000010
#0 0x7f2b80914425 base::debug::StackTrace::StackTrace()
#1 0x7f2b8091480b <unknown>
#2 0x7f2b80c3f390 <unknown>
#3 0x564e0cc8fdc8 <unknown>
#4 0x564e0cc92656 <unknown>
#5 0x564e0cc92df9 <unknown>
#6 0x564e0cc93143 <unknown>
#7 0x7f2b8098f821 <unknown>
#8 0x7f2b80915eea base::debug::TaskAnnotator::RunTask()
#9 0x7f2b8093ee90 base::MessageLoop::RunTask()
#10 0x7f2b8094097d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7f2b8094183d <unknown>
#12 0x7f2b80942300 base::MessagePumpLibevent::Run()
#13 0x7f2b8093df15 base::MessageLoop::RunHandler()
#14 0x7f2b80968628 base::RunLoop::Run()
#15 0x7f2b80994e36 base::Thread::ThreadMain()
#16 0x7f2b8098f726 <unknown>
#17 0x7f2b80c356ba start_thread
#18 0x7f2b6a2e43dd clone
  r8: 000000000000002e r9: 0000564e0e6e66ec r10: 0000000000000000 r11: 00007f2b6a371f50
 r12: 00007f2acfcd7ff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007f2acfcd7eb0
  di: 0000000000000000 si: 00007f2acfcd7eb0 bp: 00007f2acfcd7f00 bx: 00007f2acfcd7eb0
  dx: 000000000000005d ax: 0000000000000000 cx: 00007f2aa8008070 sp: 00007f2acfcd7e60
  ip: 0000564e0cc8fdc8 efl: 0000000000010206 cgf: 002b000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

ASUS ROG G750JS, Ubuntu 16.04

I tried to start in this mode:
chromium-browser --password-store=basic
As I knew it could cause issues. No help. Same error.
Same goes for a purge and reinstall
sudo apt-get purge chromium-browser / -> install

Revision history for this message
jlaustill (jlaustill) wrote :

+1 Same here

Revision history for this message
gianny007 (gianny007) wrote :

Hi I have the same issues since yestarday:

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.2 LTS
Release: 16.04
Codename: xenial
Linux mrbabbs-MacBookPro 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
chromium-browser:
  Installed: 59.0.3071.109-0ubuntu0.16.04.1289
  Candidate: 59.0.3071.109-0ubuntu0.16.04.1289
  Version table:
 *** 59.0.3071.109-0ubuntu0.16.04.1289 500
        500 http://de.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages
        500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     49.0.2623.108-0ubuntu1.1233 500
        500 http://de.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

But I have noticed that this issue appears only when I use the wifi, instead if I use the cable, chromium works fine

Revision history for this message
Mark Ehle (markehle) wrote :

Same problem here, on an HP G72 latop:

[25280:25280:0708/082555.940889:ERROR:account_tracker.cc(356)] OnGetTokenFailure: Invalid credentials.
[25280:25280:0708/082555.940982:ERROR:account_tracker.cc(356)] OnGetTokenFailure: Invalid credentials.
[25280:25311:0708/082556.884366:ERROR:cache_storage_cache.cc(1450)] Cache size: 2642261 does not match size from index: 2647189
Received signal 11 SEGV_MAPERR 000000000010
#0 0x7fd79aa4f425 base::debug::StackTrace::StackTrace()
#1 0x7fd79aa4f80b <unknown>
#2 0x7fd79ad7a390 <unknown>
#3 0x55ab357f7dc8 <unknown>
#4 0x55ab357fa656 <unknown>
#5 0x55ab357fadf9 <unknown>
#6 0x55ab357fb143 <unknown>
#7 0x7fd79aaca821 <unknown>
#8 0x7fd79aa50eea base::debug::TaskAnnotator::RunTask()
#9 0x7fd79aa79e90 base::MessageLoop::RunTask()
#10 0x7fd79aa7b97d base::MessageLoop::DeferOrRunPendingTask()
#11 0x7fd79aa7c83d <unknown>
#12 0x7fd79aa7d300 base::MessagePumpLibevent::Run()
#13 0x7fd79aa78f15 base::MessageLoop::RunHandler()
#14 0x7fd79aaa3628 base::RunLoop::Run()
#15 0x7fd79aacfe36 base::Thread::ThreadMain()
#16 0x7fd79aaca726 <unknown>
#17 0x7fd79ad706ba start_thread
#18 0x7fd78441f3dd clone
  r8: 000000000000002e r9: 000055ab3724e6ec r10: 0000000000000000 r11: 000055ab3a1ecce8
 r12: 00007fd713ffbff0 r13: 0000000000000008 r14: 0000000000000008 r15: 00007fd713ffbeb0
  di: 0000000000000000 si: 00007fd713ffbeb0 bp: 00007fd713ffbf00 bx: 00007fd713ffbeb0
  dx: 000000000000005d ax: 0000000000000000 cx: 00007fd724094aa0 sp: 00007fd713ffbe60
  ip: 000055ab357f7dc8 efl: 0000000000010206 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000010
[end of stack trace]
Calling _exit(1). Core file will not be generated.

Revision history for this message
Julien Negros (djiock) wrote :

Hi !
Same as Sam M (sam-samuel-magnan), I was browsing normally then after a crash it wouldn't work again... Should we (if not already done) fill a bug report on the Chromium project ?

Revision history for this message
Olivier Tilloy (osomon) wrote :

@Julien: this is not needed, this crash is specific to the ubuntu chromium packages, and a fix is on its way. You can track progress with bug #1702407.

Revision history for this message
kingstying@gmail.com (kingsting) wrote :

I got the same problem on my arm linux board. Does it have been resolved?

Revision history for this message
carlos (cloudspaba) wrote :

I try find a solution, execution the next command:

chromium-browser --disable-extensions

And delete the user in chromium, this method can enable the all function of chromium, and can login the user in a new rest of chromium program

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.