)]}'
{
  "commit": "3273d03562abb69b61e23fe6bfa3c7661905655e",
  "tree": "e1735b29bd60a439e7a4f1da4055fe8bcfded1a0",
  "parents": [
    "63784a578dd26880454d70797519358a2326291b"
  ],
  "author": {
    "name": "Alex Deymo",
    "email": "deymo@chromium.org",
    "time": "Thu May 29 02:29:52 2014"
  },
  "committer": {
    "name": "chrome-internal-fetch",
    "email": "chrome-internal-fetch@google.com",
    "time": "Fri May 30 01:26:02 2014"
  },
  "message": "Fix memory leak on UpdateManager\u0027s event loop wrapper.\n\nWhen an scheduled Closure is canceled, the memory associated with the\nClosure object wasn\u0027t removed, leaking its memory. This patch deletes\nthe Closure in both cases: when it is executed and when it is\ncanceled.\n\nBUG\u003dchromium:378548\nTEST\u003d`FEATURES\u003d\"test\" USE\u003d\"clang asan\" emerge-link update_engine` doesn\u0027t complain about RunFromMainLoopAfterTimeout.\n\nChange-Id: I10d8f58aaf0fb1fd746701a25f3ef0f8ccdf6c12\nReviewed-on: https://chromium-review.googlesource.com/202061\nReviewed-by: Alex Deymo \u003cdeymo@chromium.org\u003e\nCommit-Queue: Alex Deymo \u003cdeymo@chromium.org\u003e\nTested-by: Alex Deymo \u003cdeymo@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "6ae6d364ec0a8d00655178772f601d887bb0201d",
      "old_mode": 33188,
      "old_path": "update_manager/event_loop.cc",
      "new_id": "bc2940b2d3fdcda3c32eede6d0d516084f9b30b7",
      "new_mode": 33188,
      "new_path": "update_manager/event_loop.cc"
    }
  ]
}