)]}'
{
  "commit": "26b98f4271095999a721fd85f17044eb8441cc97",
  "tree": "c97f9f6030d162f657420506d466393782bb1cfd",
  "parents": [
    "d781434637535fdb283427c3d9449279166b28a9"
  ],
  "author": {
    "name": "Robert Carr",
    "email": "racarr@google.com",
    "time": "Mon Apr 11 15:54:31 2022 -0700"
  },
  "committer": {
    "name": "Robert Carr",
    "email": "racarr@google.com",
    "time": "Mon Apr 11 15:56:22 2022 -0700"
  },
  "message": "SurfaceFlinger: Dump on layer leaks\n\nEvery so often some process will leak layer references and\nSurfaceFlinger will eventually crash (or refusing to create\nnew layers because of the max layer count). We never have\nenough info to trace these down, and it becomes a horrible\ngame of chasing repro steps. While we currently have no\ncomplaints about anything like this in T, a recent\n12L bug serves as a timely reminder that we should get\nthis logging in BEFORE the next issue occurs, rather\nthan after.\n\nBug: 227286456\nTest: Existing tests pass\nChange-Id: I2c8b834c93a27204225b482fea1e54837204c9cf\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fb5d738ed9a731b170b482571398e1643146c301",
      "old_mode": 33188,
      "old_path": "services/surfaceflinger/SurfaceFlinger.cpp",
      "new_id": "ee4c41e2f663cc2aa89f5281c0580fb50c6d6363",
      "new_mode": 33188,
      "new_path": "services/surfaceflinger/SurfaceFlinger.cpp"
    }
  ]
}
