)]}'
{
  "commit": "25140afb6608c7f4ecff684ac97ee5197a02c2d3",
  "tree": "8a8f6798ce109869525b77863819a65dcdfdd9c2",
  "parents": [
    "60a4d7fab17033334dceea27d5ae708286002d4a"
  ],
  "author": {
    "name": "chiyotsai",
    "email": "chiyotsai@google.com",
    "time": "Wed Aug 07 16:12:27 2019 -0700"
  },
  "committer": {
    "name": "Chi Yo Tsai",
    "email": "chiyotsai@google.com",
    "time": "Thu Aug 08 16:14:38 2019 +0000"
  },
  "message": "Don\u0027t allocate hash_me memory for BLOCK_4X4 on 4K+\n\nOn high resolution long video sequences, the memory consumption is\ndominated by the hash table used for screen content motion estimation.\n\nSince 4K+ videos don\u0027t go to BLOCK_4X4, we don\u0027t need to store the hash\ntable at this level. This reduces the memory consumption of hash_me by\n~1/6, which is about 835MBs, or ~10% of heap memory when encode 17\nframes.\n\nBUG\u003daomedia:2453\n\nChange-Id: Ic7f4104ac55d802193444b16232ff4d48c3bf2ea\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b513ac8be6d523b1cf4f2ca9e966120f6e303e6f",
      "old_mode": 33188,
      "old_path": "av1/encoder/encodeframe.c",
      "new_id": "d21c12652a71dcf6a242380dfd57ba3eb7256657",
      "new_mode": 33188,
      "new_path": "av1/encoder/encodeframe.c"
    }
  ]
}