)]}'
{
  "commit": "ddc4e8a50f893c58f363e83841c010cde82fe4b4",
  "tree": "1141ed02a2ba5f3f55cdb651f362971cb305920f",
  "parents": [
    "7a34fcffbcf216cc7b62e21cbb6f3789e07b9cc7"
  ],
  "author": {
    "name": "Lokbondo Kung",
    "email": "lokokung@google.com",
    "time": "Thu May 28 18:56:16 2026 -0700"
  },
  "committer": {
    "name": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "dawn-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu May 28 18:56:16 2026 -0700"
  },
  "message": "[fuzz] Make sure that we teardown for fuzzer injected errors.\n\n- In https://dawn-review.git.corp.google.com/c/dawn/+/302578 I was\n  a bit aggressive at removing some of the handling for the fuzzers.\n  This change reverts it a bit to ensure that if the error injector\n  is enabled, that a DeviceLost error still forces the Vulkan\n  backend to teardown. This addresses the potential UAF found in the\n  fuzzer bug below.\n- Note that the bug shouldn\u0027t be reproducible in the wild.\n\nBug: 503873145\nChange-Id: Id53f9040078a2aea82e9621c6e7a8e7ead322097\nReviewed-on: https://dawn-review.googlesource.com/c/dawn/+/309569\nAuto-Submit: Loko Kung \u003clokokung@google.com\u003e\nReviewed-by: Kai Ninomiya \u003ckainino@chromium.org\u003e\nCommit-Queue: Loko Kung \u003clokokung@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a154bc0ddf59300e4bd620d11f2a10e35b348764",
      "old_mode": 33188,
      "old_path": "src/dawn/native/Device.cpp",
      "new_id": "9d38791dff75683c243784b0d182a450bd9d1bee",
      "new_mode": 33188,
      "new_path": "src/dawn/native/Device.cpp"
    }
  ]
}