Bug 51578 - User believes EventWaitHandle should allocate system wide handles
Summary: User believes EventWaitHandle should allocate system wide handles
Status: NEW
Alias: None
Product: Class Libraries
Classification: Mono
Component: System (show other bugs)
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2017-01-17 16:36 UTC by Chris Hamons
Modified: 2017-03-15 20:42 UTC (History)
3 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 for Bug 51578 on GitHub or Developer Community if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: GitHub Markdown or Developer Community HTML
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
NEW

Description Chris Hamons 2017-01-17 16:36:06 UTC
There is a discussion here: https://forums.xamarin.com/discussion/comment/246591

where a user believes this code:

App1:
bool createdNew;
EventWaitHandle e = new EventWaitHandle(false, EventResetMode.ManualReset, "MyEvent", out createdNew);
e.Set();

App2:
bool createdNew;
EventWaitHandle e = new EventWaitHandle(false, EventResetMode.ManualReset, "MyEvent", out createdNew);
e.WaitOne();

should work (as it does on Windows).

The MSDN documentation is unclear (in my opinion) on expected behavior, as they define as a thread sync object but then define the name property as "system-wide synchronization event".

I've filed this bug on behalf of the user as a courtesy.
Comment 1 Gergely Bacsó 2017-01-17 20:03:44 UTC
Note: the same applies to the Mutex and Semaphore classes.
Comment 2 Xavier Rigau 2017-03-15 20:42:14 UTC
I am affected by the same issue but with Mutex