Libvpx shares the compressor context between threads in a possibly dangerous manner

Chen-tao / webm

Automatically exported from code.google.com/p/webm

0 stars 0 forks source link

Libvpx shares the compressor context between threads in a possibly dangerous manner #511

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago

What is the expected behavior? What do you see instead?

TSan v2 reports potentially dangerous accesses to compressor state by multiple 
threads for Chrome's remoting component tests, which run the libvpx encoder 
multi-threaded.

See https://crbug.com/158922.

Original issue reported on code.google.com by wez@chromium.org on 11 Dec 2012 at 6:39

GoogleCodeExporter commented 9 years ago

This should be on the works now.

Original comment by albe...@google.com on 17 Jan 2013 at 11:30

Changed state: Started

GoogleCodeExporter commented 9 years ago

I think this is fixed. Jim is the owner of the Chromium bug.

Original comment by fgalli...@google.com on 16 Jan 2015 at 6:42

GoogleCodeExporter commented 9 years ago

Issue 500 has been merged into this issue.

Original comment by fgalli...@google.com on 16 Jan 2015 at 6:45