Chrome Version: ToT
OS: Linux
What steps will reproduce the problem?
(1) Build content_shell
(2) Run content_shell
What is the expected result?
content_shell launches
What happens instead?
content_shell dies with a SIGSEGV.
Received signal 11 <unknown> 000000000000
#0 0x7f7dcde6355d base::debug::StackTrace::StackTrace()
#1 0x7f7dcde6192c base::debug::StackTrace::StackTrace()
#2 0x7f7dcde62f15 base::debug::(anonymous namespace)::StackDumpSignalHandler()
#3 0x7f7dd34010c0 <unknown>
#4 0x7f7dd365673c std::__1::__tree<>::__count_unique<>()
#5 0x7f7dd364ff6b gfx::ICCProfileCache::GetAndSetNeedsHistogram()
#6 0x7f7dd364ecea gfx::ICCProfile::HistogramDisplay()
#7 0x7f7dc05ea448 views::DesktopScreenX11::BuildDisplaysFromXRandRInfo()
#8 0x7f7dc05e970d views::DesktopScreenX11::DesktopScreenX11()
#9 0x7f7dc05ec1f0 views::CreateDesktopScreen()
#10 0x000000d69bf7 content::Shell::PlatformInitialize()
#11 0x000000d338ca content::Shell::Initialize()
#12 0x000000d9d259 content::ShellBrowserMainParts::PreMainMessageLoopRun()
#13 0x7f7dcfae83e4 content::BrowserMainLoop::PreMainMessageLoopRun()
#14 0x7f7dcea5838d _ZN4base8internal13FunctorTraitsIMN7content14NetworkContextEFvvEvE6InvokeIPS3_JEEEvS5_OT_DpOT0_
#15 0x7f7dcea582d4 _ZN4base8internal12InvokeHelperILb0EvE8MakeItSoIMN7content14NetworkContextEFvvEJPS5_EEEvOT_DpOT0_
#16 0x7f7dcfaef0a5 _ZN4base8internal7InvokerINS0_9BindStateIMN7content15BrowserMainLoopEFivEJNS0_17UnretainedWrapperIS4_EEEEEFivEE7RunImplIRKS6_RKNSt3__15tupleIJS8_EEEJLm0EEEEiOT_OT0_NSF_16integer_sequenceImJXspT1_EEEE
#17 0x7f7dcfaeefec _ZN4base8internal7InvokerINS0_9BindStateIMN7content15BrowserMainLoopEFivEJNS0_17UnretainedWrapperIS4_EEEEEFivEE3RunEPNS0_13BindStateBaseE
#18 0x7f7dcea2055d _ZNKR4base17RepeatingCallbackIFvvEE3RunEv
#19 0x7f7dd08e7b8d content::StartupTaskRunner::RunAllTasksNow()
#20 0x7f7dcfae443f content::BrowserMainLoop::CreateStartupTasks()
#21 0x7f7dcfaf1414 content::BrowserMainRunnerImpl::Initialize()
#22 0x000000d38016 ShellBrowserMain()
#23 0x000000d1446e content::ShellMainDelegate::RunProcess()
#24 0x7f7dd1789549 content::RunNamedProcessTypeMain()
#25 0x7f7dd178c29e content::ContentMainRunnerImpl::Run()
#26 0x7f7dd1786d6d content::ContentServiceManagerMainDelegate::RunEmbedderProcess()
#27 0x7f7dc912a9d5 service_manager::Main()
#28 0x7f7dd178840f content::ContentMain()
#29 0x000000491b91 main
#30 0x7f7dbf5f92b1 __libc_start_main
#31 0x000000491a64 <unknown>
r8: 00000000000000fe r9: 00007ffea7f7e200 r10: 00007ffea7f7e5fe r11: 00007f7dbf742ee0
r12: 0000000000491a3b r13: 00007ffea7f80ed0 r14: 0000000000000000 r15: 0000000000000000
di: 695f5f0072747320 si: 00007f7dd3663120 bp: 00007ffea7f7e4a0 bx: 0000000000000000
dx: 0022f03cd16d4701 ax: 0022f03cd16d4701 cx: 695f5f0072747320 sp: 00007ffea7f7e400
ip: 00007f7dd365673c efl: 0000000000010202 cgf: 002b000000000033 erf: 0000000000000000
trp: 000000000000000d msk: 0000000000000000 cr2: 0000000000000000
[end of stack trace]
Calling _exit(1). Core file will not be generated.
This crash was introduced by https://chromium-review.googlesource.com/c/chromium/src/+/612252.
Comment 1 by reillyg@chromium.org
, Aug 30 2017