dagwieers/dstat — Issue #11: Process parsing of plugin 'top-oom' is incorrect
Author: eliasp
Created: 2012-01-16 16:21:50+00:00
State: open

When 'chrome' (Google Chrome or Google Chromium) is the top-oom process, the output looks like this:

moria ~ # dstat --top-oom
--out-of-memory---
kill score
--enable-expe328
--enable-expe328
--enable-expe328

This happens very likely due to the parsing of the process list in the top-oom plugin, which probably uses a regex or split matching on a `/`.

The process list entry of a running Chrome/Chromium looks like this:

29447 ? Sl 0:28 /usr/lib64/chromium-browser/chrome --type=renderer --lang=en-US --force-fieldtest=CacheListSize/CacheListSize_14/ConnCountImpact/conn_count_6/ConnnectBackupJobs/ConnectBackupJobsEnabled/DnsImpact/default_enabled_prefetch/DnsParallelism/parallel_default/GlobalSdch/global_enable_sdch/IdleSktToImpact/idle_timeout_10/Instant/InstantControlB/Prefetch/ContentPrefetchPrerender1/PrerenderFromOmniboxHeuristic/OriginalAlgorithm/ProxyConnectionImpact/proxy_connections_32/SpdyCwnd/cwnd16/SpdyImpact/npn_with_spdy/WarmSocketImpact/last_accessed_socket/ --enable-experimental-extension-apis --enable-print-preview --channel=98765.0xbeefec0de.123456789