On Sunday, 19 May 2013 at 21:02:57 UTC, Walter Bright wrote:
On 5/19/2013 11:22 AM, deadalnix wrote:
The damn thing should have been initialized in the
first place to avoid the bug.
Sounds like you have the double-checked locking bug. Using a
different value to initialize it won't fix it.
No it sound like initalizing something to null, then initialize
it properly, assume all over the place that it is initialized to
something else, and in some rare code path it blows up.
The fact that this occurs in a multithreaded environment made it
super hard to debug, but the whole thing was properly
synchronized.
Don't assume that I do not understand what the problem with
double check locking is :
http://d.puremagic.com/issues/show_bug.cgi?id=6607
