Our website uses cookies to enhance your browsing experience.
Accept
to the top
close form

Fill out the form in 2 simple steps below:

Your contact information:

Step 1
Congratulations! This is your promo code!

Desired license type:

Step 2
Team license
Enterprise license
** By clicking this button you agree to our Privacy Policy statement
close form
Request our prices
New License
License Renewal
--Select currency--
USD
EUR
* By clicking this button you agree to our Privacy Policy statement

close form
Free PVS‑Studio license for Microsoft MVP specialists
* By clicking this button you agree to our Privacy Policy statement

close form
To get the licence for your open-source project, please fill out this form
* By clicking this button you agree to our Privacy Policy statement

close form
I am interested to try it on the platforms:
* By clicking this button you agree to our Privacy Policy statement

close form
check circle
Message submitted.

Your message has been sent. We will email you at


If you haven't received our response, please do the following:
check your Spam/Junk folder and click the "Not Spam" button for our message.
This way, you won't miss messages from our team in the future.

>
>
>
Starvation

Starvation

Dec 28 2011

Starvation. Stoppage of work of one or several threads of a multithread application for an indefinite (or infinite) period. Threads which are not being scheduled for execution, even if they are not blocked and do not wait, are called starving. The cause of starvation usually lies in scheduling rules and policies. For example, if on a single-core processor we schedule a constantly working non-blocking thread with a high priority, another thread with a lesser priority will never start working.

References

  • Rahul V. Patil and Boby George. Tools And Techniques to Identify Concurrency Issues
Popular related articles


Comments (0)

Next comments next comments
close comment form