New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 893253 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 818593
Owner:
Closed: Oct 8
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug



Sign in to add a comment

dcheck in chrome!memory_instrumentation::ProcessMap::OnServicePIDReceived on Windows server core 2016

Project Member Reported by wfh@chromium.org, Oct 8

Issue description

Chrome Version: 71.0.3571.0 git rev 57c036da68105549d9ccd2f9a8b3bc9cb78c2fc8
OS: Microsoft Windows [Version 10.0.14393] Windows 2018 Core/DataCenter

[916:2612:1008/114308.730:FATAL:process_map.cc(60)] Check failed: it_and_inserted.second. .

1b 00000090`8a3ff9a0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21
0:013> kn
 # Child-SP          RetAddr           Call Site
00 00000090`8a3fd000 00007ffa`21dcb4a0 chrome!base::debug::BreakDebugger+0xd [c:\src\gclient\src\base\debug\debugger_win.cc @ 27] 
01 00000090`8a3fd030 00007ffa`21a68d1d chrome!logging::LogMessage::~LogMessage+0x390 [c:\src\gclient\src\base\logging.cc @ 856] 
02 00000090`8a3fd600 00007ffa`220e75c2 chrome!memory_instrumentation::ProcessMap::OnServicePIDReceived+0x7f [c:\src\gclient\src\services\resource_coordinator\memory_instrumentation\process_map.cc @ 61] 
03 00000090`8a3fd760 00007ffa`21e6f4e6 chrome!service_manager::mojom::ServiceManagerListenerStubDispatch::Accept+0x3a0 [c:\src\gclient\src\out\goma64\gen\services\service_manager\public\mojom\service_manager.mojom.cc @ 450] 
04 00000090`8a3fd940 00007ffa`226a5f2d chrome!mojo::InterfaceEndpointClient::HandleValidatedMessage+0x290 [c:\src\gclient\src\mojo\public\cpp\bindings\lib\interface_endpoint_client.cc @ 0] 
05 00000090`8a3fdad0 00007ffa`21e705a0 chrome!mojo::FilterChain::Accept+0x97 [c:\src\gclient\src\mojo\public\cpp\bindings\lib\filter_chain.cc @ 40] 
06 00000090`8a3fdc30 00007ffa`21e7427b chrome!mojo::InterfaceEndpointClient::HandleIncomingMessage+0x7a [c:\src\gclient\src\mojo\public\cpp\bindings\lib\interface_endpoint_client.cc @ 306] 
07 00000090`8a3fdd90 00007ffa`21e73d92 chrome!mojo::internal::MultiplexRouter::ProcessIncomingMessage+0x2d7 [c:\src\gclient\src\mojo\public\cpp\bindings\lib\multiplex_router.cc @ 868] 
08 00000090`8a3fdf20 00007ffa`226a5f2d chrome!mojo::internal::MultiplexRouter::Accept+0x15c [c:\src\gclient\src\mojo\public\cpp\bindings\lib\multiplex_router.cc @ 594] 
09 00000090`8a3fe1a0 00007ffa`21e6d576 chrome!mojo::FilterChain::Accept+0x97 [c:\src\gclient\src\mojo\public\cpp\bindings\lib\filter_chain.cc @ 40] 
0a 00000090`8a3fe300 00007ffa`21e6decd chrome!mojo::Connector::ReadSingleMessage+0x2b4 [c:\src\gclient\src\mojo\public\cpp\bindings\lib\connector.cc @ 475] 
0b 00000090`8a3fe5e0 00007ffa`21e6dd45 chrome!mojo::Connector::ReadAllAvailableMessages+0x81 [c:\src\gclient\src\mojo\public\cpp\bindings\lib\connector.cc @ 505] 
0c 00000090`8a3fe790 00007ffa`21e8243a chrome!mojo::Connector::OnHandleReadyInternal+0x89 [c:\src\gclient\src\mojo\public\cpp\bindings\lib\connector.cc @ 389] 
0d 00000090`8a3fe8f0 00007ffa`2266e9a8 chrome!mojo::SimpleWatcher::OnHandleReady+0x102 [c:\src\gclient\src\mojo\public\cpp\system\simple_watcher.cc @ 274] 
0e 00000090`8a3fea70 00007ffa`21dd69df chrome!base::debug::TaskAnnotator::RunTask+0x178 [c:\src\gclient\src\base\debug\task_annotator.cc @ 99] 
0f 00000090`8a3feca0 00007ffa`21dd6dd5 chrome!base::MessageLoop::RunTask+0x11f [c:\src\gclient\src\base\message_loop\message_loop.cc @ 436] 
10 00000090`8a3feed0 00007ffa`21dd9e75 chrome!base::MessageLoop::DoWork+0x185 [c:\src\gclient\src\base\message_loop\message_loop.cc @ 517] 
11 00000090`8a3ff100 00007ffa`21dd8a4e chrome!base::MessagePumpForIO::DoRunLoop+0xa5 [c:\src\gclient\src\base\message_loop\message_pump_win.cc @ 512] 
12 00000090`8a3ff150 00007ffa`21dd664b chrome!base::MessagePumpWin::Run+0x4e [c:\src\gclient\src\base\message_loop\message_pump_win.cc @ 54] 
13 00000090`8a3ff1a0 00007ffa`21dff149 chrome!base::MessageLoop::Run+0x8b [c:\src\gclient\src\base\message_loop\message_loop.cc @ 388] 
14 00000090`8a3ff300 00007ffa`21e1d9c8 chrome!base::RunLoop::Run+0xf9 [c:\src\gclient\src\base\run_loop.cc @ 105] 
15 00000090`8a3ff460 00007ffa`21524030 chrome!base::Thread::Run+0xc8 [c:\src\gclient\src\base\threading\thread.cc @ 262] 
16 00000090`8a3ff5c0 00007ffa`21523fb0 chrome!content::BrowserProcessSubThread::IOThreadRun+0x24 [c:\src\gclient\src\content\browser\browser_process_sub_thread.cc @ 175] 
17 00000090`8a3ff600 00007ffa`21e1dce1 chrome!content::BrowserProcessSubThread::Run+0xd2 [c:\src\gclient\src\content\browser\browser_process_sub_thread.cc @ 132] 
18 00000090`8a3ff760 00007ffa`21e1bb5c chrome!base::Thread::ThreadMain+0x2f1 [c:\src\gclient\src\base\threading\thread.cc @ 360] 
19 00000090`8a3ff8f0 00007ffa`3cde8364 chrome!base::`anonymous namespace'::ThreadFunc+0xcc [c:\src\gclient\src\base\threading\platform_thread_win.cc @ 103] 
1a 00000090`8a3ff970 00007ffa`3d845e91 KERNEL32!BaseThreadInitThunk+0x14
1b 00000090`8a3ff9a0 00000000`00000000 ntdll!RtlUserThreadStart+0x21

https://cs.chromium.org/chromium/src/services/resource_coordinator/memory_instrumentation/process_map.cc?l=60


 
Cc: primiano@chromium.org lalitm@chromium.org
+primiano, lalitm for memory_instrumentation service DCHECK.
Labels: found_with_dchecks
found while diagnosing  issue 888783 , if that helps. 

the test environment here is quite esoteric, so feel free to reach out if you need any help reproducing.
Owner: wfh@chromium.org
Status: Assigned (was: Untriaged)
I think this bug could be bogus, my renderer processes are failing to start. I am investigating this, for now leave this with me until I know what's happening here.
Status: WontFix (was: Assigned)
yes this seems to just be a DCHECK that hits when renderer processes can't be started at all... so I suppose WontFix... yay... :(
Mergedinto: 818593
Status: Duplicate (was: WontFix)
Ops sorry was at an offsite, missed this.
That is because of the callback interface of mojo service manager listener seems racy. 
A workaround for thet dcheck landed yesterday in https://bugs.chromium.org/p/chromium/issues/detail?id=818593#c13

Sign in to add a comment