)]}'
{
  "commit": "ca254eda989155f5b3a421d41e2f94c683e8f2e6",
  "tree": "8736659e00fbfdebf9aef375d3b1651c36fee323",
  "parents": [
    "091d8ec245232ab102c50d1e06a11f2bd9362e5a"
  ],
  "author": {
    "name": "wub",
    "email": "wub@google.com",
    "time": "Thu Jul 09 13:43:02 2020 -0400"
  },
  "committer": {
    "name": "Victor Vasiliev",
    "email": "vasilvv@google.com",
    "time": "Thu Jul 09 14:46:27 2020 -0400"
  },
  "message": "In quicpacketcreator::serializepacket, set encrypted_buffer.buffer to nullptr before function returns. no behavior change, not protected.\n\nThe avoid_leak_writer_buffer flags has been default enabled but can\u0027t be deprecated due to a Chrome OS test failure in b/157989434. I suspect in that test environment, the std::move-d release_buffer(a std::function) is not set to an empty state, so the destructor of encrypted_buffer is still trying free the encrypted buffer. This is not observed in other environments.\n\nPiperOrigin-RevId: 320427430\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2a9d92c088c540221fc93dfc4226a8cf574fe6bd",
      "old_mode": 33188,
      "old_path": "quic/core/quic_packet_creator.cc",
      "new_id": "d9de9ad35988ff0256bed9f8c6d5a5e0addb88ed",
      "new_mode": 33188,
      "new_path": "quic/core/quic_packet_creator.cc"
    }
  ]
}