Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Created attachment 5957 [details]
Launching many concurrent tasks with await Task.Delay(...) exhaust ThreadPool instantly, as if it just did Thread.Sleep(..) inside ThreadPool thread. Microsoft .Net behaves right. My custom implementation using TaskCompletionSource and System.Timers.Timer works right. Tested in 3.2.3 on openSUSE and CentOS.
Forgot to add, I'm using export MONO_THREADS_PER_CPU and --server key, so I've got 100 threads in ThreadPool - more than enough.
It works for me with mono master or mono 3.2.7
I can confirm the bug running on OS X 10.9.1 using Mono 3.2.6. Using Timer works for me, too.