)]}'
{
  "commit": "314d020ed68bfa0b3ae43b98870501d1a0fee15a",
  "tree": "ea1dcc79312e605b2847865c2abe41d5e13f58d0",
  "parents": [
    "038fc3f08dcdf1e169c94ac12302402a8492c8e5"
  ],
  "author": {
    "name": "Carl Zhang",
    "email": "carl.zhang@intel.com",
    "time": "Wed Dec 17 16:09:21 2025 +0800"
  },
  "committer": {
    "name": "Carl Zhang",
    "email": "carl.zhang@intel.com",
    "time": "Wed Dec 17 16:09:21 2025 +0800"
  },
  "message": "[Media Decode] dont reduce the slice number when app layer destroy SliceDataBuffer\n\nsometimes, app call vaDestoryBuffer for VASliceDataBufferType in middle of one frame execution.\nfor example: there are two VASliceDataBufferType for one frame. after first VASliceDataBufferType\nwas created. then destroy one VASliceDataBufferType of last frame , then create second slice for\ncurrent frame, it will cause problem.\nthe rootcause is :media driver try to optimize the bistream combination, so it allocate one buffer\nfor mulitple slice data. then these slice data just get the offset and were filled into one bistream\nbuffer. this method reduce one combination copy.\n\nSigned-off-by: Carl Zhang \u003ccarl.zhang@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "397e737bdf45fa0f44aa979b74ba7ff0881434eb",
      "old_mode": 33261,
      "old_path": "media_driver/linux/common/ddi/media_libva.cpp",
      "new_id": "9917cdd951231c38fa20b26e203b49e60d1c75ba",
      "new_mode": 33261,
      "new_path": "media_driver/linux/common/ddi/media_libva.cpp"
    },
    {
      "type": "modify",
      "old_id": "23fe5ba3e2738c96324025beca72b537fd365cdc",
      "old_mode": 33188,
      "old_path": "media_softlet/linux/common/codec/ddi/dec/ddi_decode_functions.cpp",
      "new_id": "7993f6977a1e53e0884bbca392039164caaed915",
      "new_mode": 33188,
      "new_path": "media_softlet/linux/common/codec/ddi/dec/ddi_decode_functions.cpp"
    }
  ]
}