chrome renderer and worker processes killed before leak scan or summary

Question

From bruen....com on August 05, 2011 16:35:53

Running WorkerFileSystemTest.Temporary we have the main chrome.exe process and two children, the renderer (not there with --single-process) and the worker (test-specific). The renderer and worker die before their error summary is printed out (presumably killed by the parent chrome process).

We need to either change how they're killed, or add an annotation ( issue #283 ) to send a nudge requesting a summary right before they are killed: simplest to have the nudge also kill to avoid needing bi-directional communication.

% ls -lt logs drwxr-xr-x+ 1 bruening Domain Users 0 Aug 5 16:23 DrMemory-chrome.exe.3608.000 drwxr-xr-x+ 1 bruening Domain Users 0 Aug 5 16:23 DrMemory-chrome.exe.5900.000 drwxr-xr-x+ 1 bruening Domain Users 0 Aug 5 16:22 DrMemory-chrome.exe.2232.000 % grep FINAL logs/DrMemory-/r logs/DrMemory-chrome.exe.2232.000/results.txt:FINAL SUMMARY:

% head -3 logs/D_/r_ ==> logs/DrMemory-chrome.exe.2232.000/results.txt <== Dr. Memory version 1.4.451 build 1 built on Aug 5 2011 16:14:33 Dr. Memory results for pid 2232: "chrome.exe" Application cmdline: ""E:\src\chromium\src\build\Debug\chrome.exe" --disable-web-resources --disable-preconnect --no-first-run --no-default-browser-check --enable-logging --log-level=1 --safebrowsing-disable-auto-update --no-default-browser-check --test-type=ui --user-data-dir="C:\Users\bruening\AppData\Local\Temp\scoped_dir3606" --testing-channel=ChromeTestingInterface:5244.1 --noerrdialogs --metrics-recording-only --enable-logging --allow-file-access-from-files --disable-tab-closeable-state-watcher --allow-file-access --unlimited-quota-for-files --use-gl=osmesa --disable-accelerated-compositing --enable-file-cookies --homepage=about:blank --test-name=WorkerFileSystemTest.Temporary"

==> logs/DrMemory-chrome.exe.5900.000/results.txt <== Dr. Memory version 1.4.451 build 1 built on Aug 5 2011 16:14:33 Dr. Memory results for pid 5900: "chrome.exe" Application cmdline: ""E:\src\chromium\src\build\Debug\chrome.exe" --type=renderer --noerrdialogs --disable-accelerated-compositing --enable-logging --log-level=1 --use-gl=osmesa --lang=en-US --force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJobs/ConnectBackupJobsEnabled/DnsImpact/default_enabled_prefetch/DnsParallelism/parallel_10/GlobalSdch/global_enable_sdch/IdleSktToImpact/idle_timeout_60/Prefetch/ContentPrefetchPrerender2/ProxyConnectionImpact/proxy_connections_32/SSLFalseStart/FalseStart_disabled/SpdyCwnd/cwnd16/SpdyImpact/npn_with_spdy/WebSocketExperiment/default/ --user-data-dir="C:\Users\bruening\AppData\Local\Temp\scoped_dir3606" --disable-client-side-phishing-detection --channel=2232.26FAB4B8.537668041 /prefetch:3"

==> logs/DrMemory-chrome.exe.3608.000/results.txt <== Dr. Memory version 1.4.451 build 1 built on Aug 5 2011 16:14:33 Dr. Memory results for pid 3608: "chrome.exe" Application cmdline: ""E:\src\chromium\src\build\Debug\chrome.exe" --type=worker --channel=2232.270674D0.1368925514 --enable-logging --log-level=1 --ignored=" --type=renderer " /prefetch:5"

Original issue: http://code.google.com/p/drmemory/issues/detail?id=544

该提问来源于开源项目：DynamoRIO/drmemory

Answer 1

From bruen....com on August 05, 2011 15:24:22

Note that this is not just a missing summary: it's a missing leak scan as well.

On Linux SIGTERM is used instead of SIGKILL, giving Memcheck a chance to do its leak scan and print its summary.

On Windows there is no simple "soft" kill from another process. Could use BroadcastSystemMessage to inform target to exit.

Dr. Memory's nudges are meant for this type of situation, though, and have been used for exactly this on Linux in the past. Re: annotation-triggers-nudge: the current API doesn't support a client nudging another process: only its own. No clean way to launch drconfig: though private loader should support that.

Summary: chrome renderer and worker processes killed before leak scan or summary