Sign in to Chhromium causes "signal 11 SEGV_MAPERR 000000000028"

Bug #1717473 reported by tagMacher
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chromium-browser (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

System info:

lsb_release -rd
Description: Ubuntu 16.04.3 LTS
Release: 16.04

apt-cache policy chromium-browser
chromium-browser:
  Installed: 60.0.3112.113-0ubuntu0.16.04.1298
  Candidate: 60.0.3112.113-0ubuntu0.16.04.1298
  Version table:
 *** 60.0.3112.113-0ubuntu0.16.04.1298 500
        500 http://download.nus.edu.sg/mirror/ubuntu xenial-updates/universe amd64 Packages
        500 http://download.nus.edu.sg/mirror/ubuntu xenial-security/universe amd64 Packages
        100 /var/lib/dpkg/status
     49.0.2623.108-0ubuntu1.1233 500
        500 http://download.nus.edu.sg/mirror/ubuntu xenial/universe amd64 Packages
----

Steps to demonstrate problem:
1. Installed chromium-browser from Ubuntu 16.04 64-bit LTS (xenial) standard repository using apt-get.
2. Chromium-browser starts up without issues and is usable.
    EXPECTED: Google sign-in page
    OBSERVED: Frame for new window (which should be Google sign-in page) flashes in momentarily and disappears, taking with it the chromium-browser window.

----

More info: Starting it in a Terminal, I was able to get the following:

user@ubuntu:~$ chromium-browser
Starting
Starting
Received signal 11 SEGV_MAPERR 000000000028
#0 0x7f33835373f7 base::debug::StackTrace::StackTrace()
#1 0x7f3383536f6f <unknown>
#2 0x7f3383cda390 <unknown>
#3 0x009ec00b9f1e <unknown>
#4 0x009ebf944984 <unknown>
#5 0x009ebf74132d <unknown>
#6 0x7f337d7fbc96 content::InterstitialPageImpl::OnDomOperationResponse()
#7 0x7f337d7fba96 <unknown>
#8 0x7f337d7fb9a0 content::InterstitialPageImpl::OnMessageReceived()
#9 0x7f337d8194f7 content::RenderFrameHostImpl::OnMessageReceived()
#10 0x7f3381213d35 IPC::ChannelProxy::Context::OnDispatchMessage()
#11 0x7f3383537ed3 base::debug::TaskAnnotator::RunTask()
#12 0x7f338356092d base::MessageLoop::RunTask()
#13 0x7f338356118b base::MessageLoop::DoWork()
#14 0x7f3383562b7a <unknown>
#15 0x7f336c7f2197 g_main_context_dispatch
#16 0x7f336c7f23f0 <unknown>
#17 0x7f336c7f249c g_main_context_iteration
#18 0x7f33835629e6 base::MessagePumpGlib::Run()
#19 0x7f338358e110 base::RunLoop::Run()
#20 0x009ebed26dd2 <unknown>
#21 0x7f337d7128b3 content::BrowserMainLoop::RunMainMessageLoopParts()
#22 0x7f337d71545d <unknown>
#23 0x7f337d70e408 content::BrowserMain()
#24 0x7f337de5bc8f <unknown>
#25 0x7f3383a9419d service_manager::Main()
#26 0x7f337de5aa62 content::ContentMain()
#27 0x009ebe6c8bac <unknown>
#28 0x7f3369dc9830 __libc_start_main
#29 0x009ebe6c8a09 <unknown>
  r8: 0000009ec2c63d80 r9: 000000000000000b r10: 0000000000000000 r11: 00007f3369f3f110
 r12: 00007ffdb51e5c20 r13: 0000009ec2cd5b80 r14: 00007f32e428f1a8 r15: 0000009ec2c09320
  di: 0000009ec2c09340 si: 0000009ec0f0a794 bp: 00007ffdb51e5c10 bx: 00007f32e428ebe0
  dx: 0000000000000000 ax: 0000000000000000 cx: ffffffffffffffe0 sp: 00007ffdb51e56a0
  ip: 0000009ec00b9f1e efl: 0000000000010246 cgf: 0000000000000033 erf: 0000000000000004
 trp: 000000000000000e msk: 0000000000000000 cr2: 0000000000000028
[end of stack trace]
Calling _exit(1). Core file will not be generated.
user@ubuntu:~$ Finishing
Finishing
Finishing

----

Further info: apport is not triggered by this crash

Revision history for this message
tagMacher (tagmacher) wrote :

This seems specific to this system - I have been able to run chromium-browser on my other laptop also with Ubuntu 16.04 64-bit LTS without any issues. One difference between the two is that the computer on which it crashes is behind a corporate firewall, though I feel this is not an issue since internet access is available through a proxy server.

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

Is the latest update (63.0.3239.84-0ubuntu0.16.04.1) still affected?

Could you please install the debug symbols for chromium (see instructions at https://wiki.ubuntu.com/Debug%20Symbol%20Packages#Getting_-dbgsym.ddeb_packages, you want chromium-browser-dbgsym) and run in a terminal to get a more complete backtrace?

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

[Expired for chromium-browser (Ubuntu) because there has been no activity for 60 days.]

Changed in chromium-browser (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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