Bug 13598 - SIGSEGV in WaitHandle.WaitAll
Summary: SIGSEGV in WaitHandle.WaitAll
Alias: None
Product: Runtime
Classification: Mono
Component: JIT ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-07-30 05:58 UTC by Marek Safar
Modified: 2016-11-28 03:13 UTC (History)
3 users (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 Marek Safar 2013-07-30 05:58:08 UTC
using System;
using System.Net;
using System.Threading;
using System.Threading.Tasks;

class C
    public static void Main()
        var mre = new ManualResetEvent(false);
        WaitHandle.WaitAll(new[] { mre });

All WaitAll/WaitAny are crashing. I think the check needs to be done in unmanaged code or it will be racy.


  at <unknown> <0xffffffff>
  at (wrapper managed-to-native) System.Threading.WaitHandle.WaitAll_internal (System.Threading.WaitHandle[],int,bool) <0xffffffff>
  at System.Threading.WaitHandle.WaitAll (System.Threading.WaitHandle[]) <0x00031>
  at C.Main () <0x0007f>
  at (wrapper runtime-invoke) object.runtime_invoke_void (object,intptr,intptr,intptr) <0xffffffff>


System.ObjectDisposedException: Safe handle has been closed
Comment 1 Miguel de Icaza [MSFT] 2016-11-28 03:13:44 UTC
This no longer reproduces for me.