Previous approach prevented double registration of the plugins, but might have caused a race condition: atomic flag was set before the plugins initialization, not after, so another thread could see garbage data even if it could read the flag set to "true". This might or might not be a root cause for the KTIJ-24983 exception, so we'll have to wait for some time before actually closing the issue.