Bug 44014 - Calling SemaphoreSlim.Wait with 0 timeout might return even though there are threads available
Summary: Calling SemaphoreSlim.Wait with 0 timeout might return even though there are ...
Status: RESOLVED NOT_ON_ROADMAP
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 3.12.0
Hardware: PC Linux
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2016-09-06 12:28 UTC by eb1
Modified: 2016-09-06 14:00 UTC (History)
2 users (show)

Tags:
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:
Status:
RESOLVED NOT_ON_ROADMAP

Description eb1 2016-09-06 12:28:54 UTC
SemaphoreSlim.Wait(0) might return `false` even though there are still several threads available. This can happen when the server is under load.

See also https://jira.mongodb.org/browse/CSHARP-1144

Note that this occurs only with Mono 3.x.
Comment 1 Alexander Köplinger [MSFT] 2016-09-06 13:55:19 UTC
So it doesn't occur with Mono 4.x? Mono 3.x is no longer supported.
Comment 2 eb1 2016-09-06 13:59:20 UTC
No, doesn't seem to occur with Mono 4.x
Comment 3 Alexander Köplinger [MSFT] 2016-09-06 14:00:32 UTC
Ok thanks. As I said, we don't plan on fixing bugs in Mono 3.x anymore.