[Issue 5488] Spawned threads hang in a way that suggests allocation or gc issue
d-bugmail at puremagic.com
d-bugmail at puremagic.com
Mon Jan 31 11:30:48 PST 2011
http://d.puremagic.com/issues/show_bug.cgi?id=5488
--- Comment #3 from Sean Kelly <sean at 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
the lock until thread_resumeAll() completes. This also allows me to remove
some busy waits I'd added to Thread.add() to avoid adding a thread or context
while a GC cycle was in progress. Much neater and in theory it solves
everything.
That said, I'm still seeing a rare occasional deadlock in the attached app.
This one appears to be different however, and the near complete lack of usable
debug info in DMD binaries on OSX is complicating figuring this one out. I'll
add some printfs and hope that turns up something.
--
Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
More information about the Digitalmars-d-bugs
mailing list