)]}'
{
  "commit": "a5ebd39f8583016398b6a5cd84e803c3f90035dc",
  "tree": "a5e40950e1bd69e36ae48af8c2084310434e1f4f",
  "parents": [
    "6106c97ef442846155e07a86908df1a6e14a0172"
  ],
  "author": {
    "name": "Carsten Hammer",
    "email": "carsten.hammer@t-online.de",
    "time": "Sun Dec 06 17:12:49 2020 +0100"
  },
  "committer": {
    "name": "Alexander Kurtakov",
    "email": "akurtako@redhat.com",
    "time": "Wed Jul 21 08:04:37 2021 -0400"
  },
  "message": "Bug: Incorrect lazy initialization of static field\n\norg.eclipse.help.internal.base.scope.ScopeRegistry.instance in\norg.eclipse.help.internal.base.scope.ScopeRegistry.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: I232f050bbbc83403c4b7346cb411ec47b74f19fd\nSigned-off-by: Carsten Hammer \u003ccarsten.hammer@t-online.de\u003e\nReviewed-on: https://git.eclipse.org/r/c/platform/eclipse.platform.ua/+/173454\nTested-by: Platform Bot \u003cplatform-bot@eclipse.org\u003e\nReviewed-by: Alexander Kurtakov \u003cakurtako@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "255738d2fb2ed33944b50ecd41720f4330d575a2",
      "old_mode": 33188,
      "old_path": "org.eclipse.help.base/src/org/eclipse/help/internal/base/scope/ScopeRegistry.java",
      "new_id": "cfbe9e9fb194ac22330aec23d27197210740a6ab",
      "new_mode": 33188,
      "new_path": "org.eclipse.help.base/src/org/eclipse/help/internal/base/scope/ScopeRegistry.java"
    }
  ]
}