https://issues.dlang.org/show_bug.cgi?id=5488
berni44 changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=5488
SomeDude lovelyd...@mailmetrash.com changed:
What|Removed |Added
CC|
http://d.puremagic.com/issues/show_bug.cgi?id=5488
--- Comment #5 from Sean Kelly s...@invisibleduck.org 2011-02-02 12:10:21 PST
---
Okay, all issues related to this appear to have been fixed and changes checked
in.
--
Configure issuemail:
http://d.puremagic.com/issues/show_bug.cgi?id=5488
Sean Kelly s...@invisibleduck.org changed:
What|Removed |Added
Status|NEW |ASSIGNED
http://d.puremagic.com/issues/show_bug.cgi?id=5488
--- Comment #2 from Sean Kelly s...@invisibleduck.org 2011-01-31 11:16:51 PST
---
After some testing, it looks like I was right. I have a fix for this, but it's
far from ideal (though the diff is small): require everything but
http://d.puremagic.com/issues/show_bug.cgi?id=5488
--- Comment #3 from Sean Kelly s...@invisibleduck.org 2011-01-31 11:28:35 PST
---
Okay, I decided to use a Mutex instead of a built-in object monitor for locking
the thread list, because this allows me to lock in thread_suspendAll() and hold
http://d.puremagic.com/issues/show_bug.cgi?id=5488
--- Comment #4 from Sean Kelly s...@invisibleduck.org 2011-01-31 12:02:19 PST
---
I've confirmed that this new deadlock isn't because the GC thread was blocked
acquiring the global thread list mutex, so I've fixed the issue this ticket was
