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)

See Also:
Tags:
Is this bug a regression?: ---
Last known good build:


Attachments

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

Note You need to log in before you can comment on or make changes to this bug.