chromium-browser crashes soon after execution - Received signal 11 SEGV_MAPERR 000000000010
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:
#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:
#9 0x7f5c4b957e90 base::MessageLo
#10 0x7f5c4b95997d base::MessageLo
#11 0x7f5c4b95a83d <unknown>
#12 0x7f5c4b95b300 base::MessagePu
#13 0x7f5c4b956f15 base::MessageLo
#14 0x7f5c4b981628 base::RunLoop:
#15 0x7f5c4b9ade36 base::Thread:
#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:
A Parser-blocking, cross site (i.e. different eTLD+1) script, https:/
A Parser-blocking, cross site (i.e. different eTLD+1) script, https:/
Received signal 11 SEGV_MAPERR 000000000010
#0 0x7f3a02096425 base::debug:
#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:
#9 0x7f3a020c0e90 base::MessageLo
#10 0x7f3a020c297d base::MessageLo
#11 0x7f3a020c383d <unknown>
#12 0x7f3a020c4300 base::MessagePu
#13 0x7f3a020bff15 base::MessageLo
#14 0x7f3a020ea628 base::RunLoop:
#15 0x7f3a02116e36 base::Thread:
#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
- Assignee:
- No assignee Edit question
- Solved by:
- Manfred Hampl
- Solved:
- Last query:
- Last reply:
This question was originally filed as bug #1702501.