http://bugs.winehq.org/show_bug.cgi?id=19854
--- Comment #3 from Kevin Meyer billy65bob@gmail.com 2009-08-27 18:02:02 --- (In reply to comment #2)
Created an attachment (id=23275)
--> (http://bugs.winehq.org/attachment.cgi?id=23275) [details]
Patch: Don't crash if sample allocation fails
Here's one that I think is stylistically better, though it doesn't resolve the question of when the sample is freed. Does it work for you?
Thanks for that, it does the trick nicely and judging by newer debug messages, prevented at least 8 NULLs being passed to the functions. (of which 1 message was that for the original fixme)
On the other hand, this 'bug' seems to be the sort that occurs when processes are multithreaded. ( as in, another thread is modifying the buffer for this thread, while this thread is busy working with it) does this mean there's simply a lack of relevant thread safety (mainly with (un)locking mutexes) within the processing functions? or is something else at work here?