Sign in to Chhromium causes "signal 11 SEGV_MAPERR 000000000028"
| 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.
Candidate: 60.0.3112.
Version table:
*** 60.0.3112.
500 http://
500 http://
100 /var/lib/
49.
500 http://
----
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:
#1 0x7f3383536f6f <unknown>
#2 0x7f3383cda390 <unknown>
#3 0x009ec00b9f1e <unknown>
#4 0x009ebf944984 <unknown>
#5 0x009ebf74132d <unknown>
#6 0x7f337d7fbc96 content:
#7 0x7f337d7fba96 <unknown>
#8 0x7f337d7fb9a0 content:
#9 0x7f337d8194f7 content:
#10 0x7f3381213d35 IPC::ChannelPro
#11 0x7f3383537ed3 base::debug:
#12 0x7f338356092d base::MessageLo
#13 0x7f338356118b base::MessageLo
#14 0x7f3383562b7a <unknown>
#15 0x7f336c7f2197 g_main_
#16 0x7f336c7f23f0 <unknown>
#17 0x7f336c7f249c g_main_
#18 0x7f33835629e6 base::MessagePu
#19 0x7f338358e110 base::RunLoop:
#20 0x009ebed26dd2 <unknown>
#21 0x7f337d7128b3 content:
#22 0x7f337d71545d <unknown>
#23 0x7f337d70e408 content:
#24 0x7f337de5bc8f <unknown>
#25 0x7f3383a9419d service_
#26 0x7f337de5aa62 content:
#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
| tagMacher (tagmacher) wrote | #1 |
| Olivier Tilloy (osomon) wrote | #2 |
| Changed in chromium-browser (Ubuntu): | |
| status: | New → Incomplete |
| Launchpad Janitor (janitor) wrote | #3 |
| Changed in chromium-browser (Ubuntu): | |
| status: | Incomplete → Expired |
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.