)]}'
{
  "commit": "daa0cc047acd570fbd5c127db4262e1a98637eb7",
  "tree": "7f2f8987121d6828801605fe475bdc857cdde677",
  "parents": [
    "a730eaad3386be11a372f6c974e02c8fe8c49107"
  ],
  "author": {
    "name": "Lokbondo Kung",
    "email": "lokokung@google.com",
    "time": "Fri Aug 21 11:13:48 2026 -0700"
  },
  "committer": {
    "name": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Aug 21 11:13:48 2026 -0700"
  },
  "message": "[vulkan] Add workaround for UAF in DestroyDescriptorPool.\n\n- As per the bug and the related internal Android issue,\n  this works around a temporary issue in the IMG driver\n  that causes a UAF when we attempt to call\n  AllocateDescriptorSets and run into an OOM.\n- The more \"proper\" fix would probably be to implement\n  suballocations, but since that is a much larger effort,\n  this is a band-aid fix to avoid the UAF issue for now.\n- Note that since the error that is generated is an\n  internal error, this eventually leads to a device loss\n  so it is acceptable to skip the Destroy call in this\n  case since even if it would lead to a leak, it cannot\n  propagate further.\n\nBug: 549311485\nChange-Id: I8c951e879bb405943698c179962275687e828168\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/334695\nReviewed-by: Kai Ninomiya \u003ckainino@chromium.org\u003e\nCommit-Queue: Loko Kung \u003clokokung@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ed365828e402e9df34f1befe8215ff9443f64620",
      "old_mode": 33188,
      "old_path": "src/dawn/native/vulkan/DescriptorSetAllocator.cpp",
      "new_id": "d14b23eedf635bada32f7b8f017b48eed69a2007",
      "new_mode": 33188,
      "new_path": "src/dawn/native/vulkan/DescriptorSetAllocator.cpp"
    }
  ]
}