You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (Jira)" <ji...@apache.org> on 2019/09/04 03:23:00 UTC
[jira] [Assigned] (SOLR-13705) Double-checked Locking Should Not be
Used
[ https://issues.apache.org/jira/browse/SOLR-13705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Smiley reassigned SOLR-13705:
-----------------------------------
Assignee: David Smiley
> Double-checked Locking Should Not be Used
> -----------------------------------------
>
> Key: SOLR-13705
> URL: https://issues.apache.org/jira/browse/SOLR-13705
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.2
> Reporter: Furkan KAMACI
> Assignee: David Smiley
> Priority: Major
> Fix For: 8.3
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Using double-checked locking for the lazy initialization of any other type of primitive or mutable object risks a second thread using an uninitialized or partially initialized member while the first thread is still creating it, and crashing the program.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org