commit 1eb44a83321a225974816fff2a0739e4601be45a
author maruel@chromium.org <maruel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> Wed Aug 22 11:59:51 2012
committer maruel@chromium.org <maruel@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> Wed Aug 22 11:59:51 2012
tree c958477ba83d947b374723e13cd5224feffbeb0c
parent 03cfc5bd27b5cfbf09d28f5089c1b410c4b55118

Fix LogMan tracer to work correctly when process ids are reused.

Reproduced with:
  isolate.py trace -r .../net_unittests.results
  isolate.py read -r .../net_unittests.results

It happens randomly whenever Windows decides to reuse a process id so it tends
to happens often with browser_tests.

This happened because stale processes are not removed from the map but set to
None instead.

R=cmp@chromium.org
NOTRY=true
BUG=


Review URL: https://chromiumcodereview.appspot.com/10824409

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152755 0039d316-1c4b-4281-b951-d872f2087c98