Add website to message with process id when running with --renderer-startup-dialog |
||
Issue descriptionWhen running chrome with --site-per-process we spawn a new process for different sites. This makes debugging the child process renderers difficult, especially in tests where there's no process UI to figure out which PID which site got. We should add the site to the message if possible, then you could easily attach to the renderer of the site you wanted to debug and resume the other processes. https://cs.chromium.org/chromium/src/content/renderer/renderer_main.cc?type=cs&q=ChildProcess::WaitForDebugger&l=81
,
Dec 15 2017
Moving from untriaged to assigned since iclelland@ is assigned. But I don't think this is really Blink>Infra. haraken@, you're in the OWNERS file closest to content/renderer/renderer_main.cc, what component should this go in?
,
Jun 28 2018
When I last looked into this the WaitForDebugger call happens way before we know where that process will be navigating. The more pragmatic thing may be to add a flag which outputs the PID and address each time a frame navigates. You could then grep for this from the output and use rr replay to debug the correct process. |
||
►
Sign in to add a comment |
||
Comment 1 by lunalu@chromium.org
, Jun 12 2017