Bug 362 - Self suspend is racy
Summary: Self suspend is racy
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2011-08-22 12:55 UTC by Rodrigo Kumpera
Modified: 2016-04-19 08:17 UTC (History)
1 user (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Rodrigo Kumpera 2011-08-22 12:55:02 UTC
Self suspend is racy in the way it makes the thread state available for others.

Right now we drop the thread lock before suspending, which creates a window into which the thread state say's it's suspended but, at the same, time it's not.

The solution is to atomically release the lock and wait for resume.

the decent way to do it is using a condvar, which requires us to move clr state management to MonoThreadInfo so a single lock can be used.
Comment 1 Rodrigo Kumpera 2016-04-19 08:17:44 UTC
This was fixed using a 2 stage self suspend