diff options
| author | scherkus@chromium.org <scherkus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-04-21 17:06:43 +0000 |
|---|---|---|
| committer | scherkus@chromium.org <scherkus@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-04-21 17:06:43 +0000 |
| commit | a5c9c5758bd83b035323493a5f46d18c9335b91d (patch) | |
| tree | 337a89ae05b865a7993dcf75d97f8f57e2956473 /base/platform_thread_posix.cc | |
| parent | bef59426532a5823b90fcaaade7e7504708e23f2 (diff) | |
| download | chromium_src-a5c9c5758bd83b035323493a5f46d18c9335b91d.zip chromium_src-a5c9c5758bd83b035323493a5f46d18c9335b91d.tar.gz chromium_src-a5c9c5758bd83b035323493a5f46d18c9335b91d.tar.bz2 | |
Fixes FFmpegDemuxerTest.ReadAndSeek test flakiness by using a WaitableEvent.
Turns out it was the test code that was flaky and not a threading bug in our actual code. Under heavy load it was possible for a thread holding onto a reference to get time sliced long enough that the unit test continued executing until it asserted that the object was deleted when in fact it was not.
BUG=10653
Review URL: http://codereview.chromium.org/88010
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@14113 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'base/platform_thread_posix.cc')
0 files changed, 0 insertions, 0 deletions