)]}'
{
  "commit": "4b39ef1b618b376c6ce372aaa3cf3a43d7587d9e",
  "tree": "0eddaf1d3ac99954550c79ecc0b82e0263f243cf",
  "parents": [
    "07c08ed5ddad4744c7eb9283d9f12e553a1c3f82"
  ],
  "author": {
    "name": "Carsten Hammer",
    "email": "carsten.hammer@t-online.de",
    "time": "Sun Dec 06 17:16:37 2020 +0100"
  },
  "committer": {
    "name": "Alexander Kurtakov",
    "email": "akurtako@redhat.com",
    "time": "Tue Jul 20 15:16:10 2021 -0400"
  },
  "message": "Bug: Incorrect lazy initialization of static field\n\norg.eclipse.help.internal.browser.BrowserLog.instance in\norg.eclipse.help.internal.browser.BrowserLog.getInstance()\n\nThis method contains an unsynchronized lazy initialization of a\nnon-volatile static field. Because the compiler or processor may reorder\ninstructions, threads are not guaranteed to see a completely initialized\nobject, if the method can be called by multiple threads. You can make\nthe field volatile to correct the problem. For more information, see the\nJava Memory Model web site.\n\nRank: Troubling (14), confidence: Normal\nPattern: LI_LAZY_INIT_STATIC\nType: LI, Category: MT_CORRECTNESS (Multithreaded correctness)\n\nChange-Id: I63fa84d9dd0e402e51fd948d2891534d7a0d087c\nSigned-off-by: Carsten Hammer \u003ccarsten.hammer@t-online.de\u003e\nReviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.ua/+/173455\nTested-by: Platform Bot \u003cplatform-bot@eclipse.org\u003e\nReviewed-by: Alexander Kurtakov \u003cakurtako@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "173162280f2bcf6a162794cb9900b131c1e4a533",
      "old_mode": 33188,
      "old_path": "org.eclipse.help.base/src/org/eclipse/help/internal/browser/BrowserLog.java",
      "new_id": "9ea5ccf858d06530048781cf92a13fbadc615036",
      "new_mode": 33188,
      "new_path": "org.eclipse.help.base/src/org/eclipse/help/internal/browser/BrowserLog.java"
    }
  ]
}