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

Asked by Rohan Bayer-Fox on 2017-07-05

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.

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu chromium-browser Edit question
Assignee:
No assignee Edit question
Solved by:
Manfred Hampl
Solved:
2017-07-06
Last query:
2017-07-06
Last reply:
2017-07-06
Rohan Bayer-Fox (rbayerfox) said : #1

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

If you have a bug then you don't need a question as well

Rohan Bayer-Fox (rbayerfox) said : #3

Thanks. I suspect a bug, but also suspect that I am doing something wrong, or that there are other things to try before I report it as a bug.

Olivier Tilloy (osomon) said : #4

Opening a bug was the right thing to do. Could you please install the debug symbols for chromium (following the instructions at https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Debug_Symbol_Packages) and see if you get a more complete stacktrace?

Rohan Bayer-Fox (rbayerfox) said : #5

I added the new repositories but cannot figure out how to resolve the dependencies for chromium-browser-dbg. I get:chromium-browser-dbg:
  Depends: chromium-browser (=51.0.2704.79-0ubuntu0.16.04.1.1242) but 59.0.3071.109-0ubuntu0.16.04.1289 is to be installed

---------- Original Message ----------
From: Olivier Tilloy <email address hidden>
To: <email address hidden>
Subject: Re: [Question #646254]: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
Date: Wed, 05 Jul 2017 18:37:40 -0000

Your question #646254 on chromium-browser in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

    Status: Open => Needs information

Olivier Tilloy requested more information:
Opening a bug was the right thing to do. Could you please install the
debug symbols for chromium (following the instructions at
https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Debug_Symbol_Packages)
and see if you get a more complete stacktrace?

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

You received this question notification because you asked the question.
____________________________________________________________
(7) Signs That Your Body Is Fighting Cancer (Photos)
obviouslybored.com
http://thirdpartyoffers.juno.com/TGL3131/595d3cb6e910a3cb66d57st04vuc

Rohan Bayer-Fox (rbayerfox) said : #6

I also loaded chromium-browser-dbgsym, but it will not run. Sorry about this - it's my first attempt at this.

---------- Original Message ----------
From: Olivier Tilloy <email address hidden>
To: <email address hidden>
Subject: Re: [Question #646254]: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
Date: Wed, 05 Jul 2017 18:37:40 -0000

Your question #646254 on chromium-browser in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

    Status: Open => Needs information

Olivier Tilloy requested more information:
Opening a bug was the right thing to do. Could you please install the
debug symbols for chromium (following the instructions at
https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Debug_Symbol_Packages)
and see if you get a more complete stacktrace?

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

You received this question notification because you asked the question.

____________________________________________________________
Affordable Wireless Plans
Set up is easy. Get online in minutes.
Starting at only $14.95 per month!
www.netzero.net?refcd=nzmem0216

Rohan Bayer-Fox (rbayerfox) said : #7

I struggled for 2 hours trying to figure out the instructions for loading/running debug symbols; I failed. If you can send simple instructions to get the trace you need, I would be glad to run it.

---------- Original Message ----------
From: Olivier Tilloy <email address hidden>
To: <email address hidden>
Subject: Re: [Question #646254]: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
Date: Wed, 05 Jul 2017 18:37:40 -0000

Your question #646254 on chromium-browser in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

    Status: Open => Needs information

Olivier Tilloy requested more information:
Opening a bug was the right thing to do. Could you please install the
debug symbols for chromium (following the instructions at
https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Debug_Symbol_Packages)
and see if you get a more complete stacktrace?

--
To answer this request for more information, you can either reply to
this email or enter your reply at the following page:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

You received this question notification because you asked the question.
____________________________________________________________
3 Common Foods Surgeons Are Now Calling "Death Foods"
3 Harmful Foods
http://thirdpartyoffers.juno.com/TGL3131/595e2decbc0772dec3f59st04vuc

Best Manfred Hampl (m-hampl) said : #8

For the dbgsym packages:

Have you added lines for http://ddebs.ubuntu.com... to your package management configuration?
Maybe you missed adding xenial-updates and/or xenial-security lines.

In my opinion the listed repositories for the ddebs server have to exactly match the settings for the normal servers.
https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Debug_Symbol_Packages is not going enough into details about that and releasename-security is missing.

Rohan Bayer-Fox (rbayerfox) said : #9

I do seem to be missing some lines, and have not yet figured out how to use synaptic to add the repositories - composing APT line. Still, it seems that the solving of the problem has already outrun my meager ability to gather evidence, so I'll quit now. Many thanks for your guidance.

---------- Original Message ----------
From: Manfred Hampl <email address hidden>
To: <email address hidden>
Subject: Re: [Question #646254]: chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
Date: Thu, 06 Jul 2017 13:37:29 -0000

Your question #646254 on chromium-browser in Ubuntu changed:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

    Status: Open => Answered

Manfred Hampl proposed the following answer:
For the dbgsym packages:

Have you added lines for http://ddebs.ubuntu.com... to your package management configuration?
Maybe you missed adding xenial-updates and/or xenial-security lines.

In my opinion the listed repositories for the ddebs server have to exactly match the settings for the normal servers.
https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Debug_Symbol_Packages is not going enough into details about that and releasename-security is missing.

--
If this answers your question, please go to the following page to let us
know that it is solved:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254/+confirm?answer_id=7

If you still need help, you can reply to this email or go to the
following page to enter your feedback:
https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/646254

You received this question notification because you asked the question.

____________________________________________________________
Affordable Wireless Plans
Set up is easy. Get online in minutes.
Starting at only $14.95 per month!
www.netzero.net?refcd=nzmem0216

Rohan Bayer-Fox (rbayerfox) said : #10

Thanks Manfred Hampl, that solved my question.