Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(73)

Issue 10824409: Fix LogMan tracer to work correctly when process ids are reused. (Closed)

Created:
8 years, 4 months ago by M-A Ruel
Modified:
8 years, 4 months ago
Reviewers:
cmp
CC:
chromium-reviews, pam+watch_chromium.org, csharp
Visibility:
Public.

Description

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= Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=152755

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+2 lines, -2 lines) Patch
M tools/isolate/trace_inputs.py View 2 chunks +2 lines, -2 lines 0 comments Download

Messages

Total messages: 4 (0 generated)
M-A Ruel
8 years, 4 months ago (2012-08-21 21:22:35 UTC) #1
cmp
lgtm, nice
8 years, 4 months ago (2012-08-22 07:42:41 UTC) #2
commit-bot: I haz the power
CQ is trying da patch. Follow status at https://chromium-status.appspot.com/cq/maruel@chromium.org/10824409/1
8 years, 4 months ago (2012-08-22 11:59:13 UTC) #3
commit-bot: I haz the power
8 years, 4 months ago (2012-08-22 11:59:53 UTC) #4
Change committed as 152755

Powered by Google App Engine
This is Rietveld 408576698