)]}'
{
  "commit": "0042e4516ffcea66cb209d8c2dad7aeaa53b50fb",
  "tree": "eca184b0eabb5bbf9fa76a233032a3fd6ba186aa",
  "parents": [
    "a2e28a4b86409415e84d36fcc072e6c3c2f0e561"
  ],
  "author": {
    "name": "wilsonshih",
    "email": "wilsonshih@google.com",
    "time": "Mon Aug 20 10:36:25 2018 +0800"
  },
  "committer": {
    "name": "wilsonshih",
    "email": "wilsonshih@google.com",
    "time": "Wed Aug 22 09:43:55 2018 +0800"
  },
  "message": "Prevent ViewRootImpl.mDisplay become null.\n\nFor some timing cases client side may not get desired display with old\ndisplayId.\nFor this issue, client side has just received configuration change and\nhandle it in ActivityThread#handleActivityConfigurationChanged. At the\nsame time, DisplayManagerService was about to destory display. When\nViewRootImpl want to update display with new DisplayAdjustments, it got\nnull because the old displayId was removed.\nFor this scenario, fallback to use default display. Usually there should\nbe other displayId change event comes from server side to ask client update.\n\nChange-Id: Ifb843f82b753761cb6306e7482b38a0ffd89498d\nFix: 73558361\nTest: atest CtsWindowManagerDeviceTestCases\nTest: atest CtsActivityManagerDeviceTestCases\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "23fc4d5045a9a1f0f0fb1c0501ae57ef877fcaf6",
      "old_mode": 33188,
      "old_path": "core/java/android/view/ViewRootImpl.java",
      "new_id": "1351f6f1ef268d06f0fb8829827d41c635e08b49",
      "new_mode": 33188,
      "new_path": "core/java/android/view/ViewRootImpl.java"
    }
  ]
}