Bug 7400 - AutoResetEvent, WaitHandle.WaitAll bug on Windows & CygWin
Summary: AutoResetEvent, WaitHandle.WaitAll bug on Windows & CygWin
Status: RESOLVED NORESPONSE
Alias: None
Product: Runtime
Classification: Mono
Component: Interop ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-09-22 20:13 UTC by Gerardo Recinto
Modified: 2017-07-07 19:00 UTC (History)
5 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 NORESPONSE

Description Gerardo Recinto 2012-09-22 20:13:14 UTC
The AutoResetEvent event signalling & WaitHandle.WaitAll event signal reception "seems" not behaving correctly in Windows 7 64 running via CygWin.

I am porting my c# (.net 4 compiled) code library to mono 2.10.8 and when I run it in MonoDevelop using Mono's .net 4 System.dll, System.Xml the auto reset event signalling and/or the WaitAll seems not working correctly together or individually.

Is this environment supported? Do I need to run/debug my apps on real Linux system instead?
My code is a simple multi-threaded app using Asynchronous FileStream I/O, employing AutoResetEvent to signal to controller thread I/O completion. Controller thread uses WaitHandle.WaitAll on array of AutoResetEvent that were dispatched to threads for signalling I/O completion.

Thx much for any help or information on this (potential) issue.
-G.
Comment 1 Zoltan Varga 2012-09-27 14:20:43 UTC
Could you attach a test case ?
Comment 2 Zoltan Varga 2013-08-20 19:31:57 UTC
-> NEEDINFO.
Comment 3 Ludovic Henry 2017-07-07 19:00:45 UTC
If you can still reproduce with latest mono version, please feel free to reopen the bug. Thank you.