Why do condition variables sometimes erroneously wake up?

Posted by aspo on Stack Overflow See other posts from Stack Overflow or by aspo
Published on 2010-04-28T06:24:18Z Indexed on 2010/04/28 6:33 UTC
Read the original article Hit count: 281

Filed under:

concurrency

|

condition-variables

I've known for eons that the way you use a condition variable is

lock
while not task_done
  wait on condition variable
unlock

Because sometimes condition variables will spontaneously wake. But I've never understood why that's the case. In the past I've read it's expensive to make a condition variable that doesn't have that behavior, but nothing more than that.

So... why do you need to worry about falsely being woken up when waiting on a condition variable?

© Stack Overflow or respective owner

Related posts about concurrency

SQL SERVER – Concurrency Basics – Guest Post by Vinod Kumar

as seen on SQL Authority - Search for 'SQL Authority'
This guest post is by Vinod Kumar. Vinod Kumar has worked with SQL Server extensively since joining the industry over a decade ago. Working on various versions from SQL Server 7.0, Oracle 7.3 and other database technologies – he now works with the Microsoft Technology Center (MTC) as a Technology… >>> More
Http requests / concurrency?

as seen on Stack Overflow - Search for 'Stack Overflow'
Say a website on my localhost takes about 3 seconds to do each request. This is fine, and as expected (as it is doing some fancy networking behind the scenes). However, if i open the same url in tabs (in firefox), then reload them all at the same time, it appears to load each page sequentially rather… >>> More
Mnesia: A Distributed DBMS Rooted in Concurrency

as seen on Internet.com - Search for 'Internet.com'
Find out what makes Mnesia, the Erlang-based database management system, perfect for distribution across a network of computers. >>> More
C# concurrency vs Java concurrency, which is neatly designed? which is better?

as seen on Stack Overflow - Search for 'Stack Overflow'
I am hard core fan for Doug Lee and his concurrency framework. I have also (from twitter) came across a comment from Joshua Bloch that java concurrency is one of the best framework (guess that he compared to .Net). But some of you worked in both Java Concurrency and .NET concurrency. What is your… >>> More
Queued Loadtest to remove Concurrency issues using Shared Data Service in OpenScript

as seen on Oracle Blogs - Search for 'Oracle Blogs'
Queued Processing to remove Concurrency issues in Loadtest ScriptsSome scripts act on information returned by the server, e.g. act on first item in the returned list of pending tasks/actions. This may lead to concurrency issues if the virtual users simulated in a load test scenario are not synchronized… >>> More

Related posts about condition-variables

Why do condition variables sometimes erroneously wake up?

as seen on Stack Overflow - Search for 'Stack Overflow'
I've known for eons that the way you use a condition variable is lock while not task_done wait on condition variable unlock Because sometimes condition variables will spontaneously wake. But I've never understood why that's the case. In the past I've read it's expensive to make a condition… >>> More
pthread condition variables on Linux, odd behaviour.

as seen on Stack Overflow - Search for 'Stack Overflow'
Hi. I'm synchronizing reader and writer processes on Linux. I have 0 or more process (the readers) that need to sleep until they are woken up, read a resource, go back to sleep and so on. Please note I don't know how many reader processes are up at any moment. I have one process (the writer) that… >>> More
What are common uses of condition variables in C++?

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm trying to learn about condition variables. I would like to know what are the common situations where condition variables are used. One example is in a blocking queue, where two threads access the queue - the producer thread pushes an item into the queue, while the consumer thread pops an item… >>> More
Wait on multiple condition variables on Linux without unnecessary sleeps?

as seen on Stack Overflow - Search for 'Stack Overflow'
I'm writing a latency sensitive app that in effect wants to wait on multiple condition variables at once. I've read before of several ways to get this functionality on Linux (apparently this is builtin on Windows), but none of them seem suitable for my app. The methods I know of are: Have one thread… >>> More
Do condition variables still need a mutex if you're changing the checked value atomically?

as seen on Stack Overflow - Search for 'Stack Overflow'
Here is the typical way to use a condition variable: // The reader(s) lock(some_mutex); if(protected_by_mutex_var != desired_value) some_condition.wait(some_mutex); unlock(some_mutex); // The writer lock(some_mutex); protected_by_mutex_var = desired_value; unlock(some_mutex); some_condition… >>> More