[chromium-bugs] Issue 23579 in chromium: Potential thread unsafeness with CoreAudio

2009-10-07 Thread codesite-noreply
Updates: Status: Fixed Comment #8 on issue 23579 by scher...@chromium.org: Potential thread unsafeness with CoreAudio http://code.google.com/p/chromium/issues/detail?id=23579 suppression committed http://src.chromium.org/viewvc/chrome?view=rev&revision=28288 -- You received this messa

[chromium-bugs] Issue 23579 in chromium: Potential thread unsafeness with CoreAudio

2009-10-05 Thread codesite-noreply
Comment #7 on issue 23579 by ramosian.glider: Potential thread unsafeness with CoreAudio http://code.google.com/p/chromium/issues/detail?id=23579 @6 Well, these are not actually recursive locks, since one can take a CAMutex several times within one thread, but it's enough to release it only

[chromium-bugs] Issue 23579 in chromium: Potential thread unsafeness with CoreAudio

2009-10-02 Thread codesite-noreply
Comment #2 on issue 23579 by ramosian.glider: Potential thread unsafeness with CoreAudio http://code.google.com/p/chromium/issues/detail?id=23579 It looks like there is a real data race in CAMutex implementation. I don't know whether its source is publicly available, but I've found http://go