Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Resetting a <code>ManualResetEvent</code> is not like calling <code>Monitor.Pulse</code> - it makes no guarantee that it will release any particular number of threads. On the contrary, the documentation (for the underlying Win32 synchronization primitive) is pretty clear that you can't know what will happen:</p> <blockquote> <p>Any number of waiting threads, or threads that subsequently begin wait operations for the specified event object, can be released while the object's state is signaled</p> </blockquote> <p>The key phrase here is "any number" which includes zero.</p> <p>Win32 does provide a <code>PulseEvent</code> but as it says "This function is unreliable and should not be used." The remarks in its documentation at <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/ms684914(v=vs.85).aspx">http://msdn.microsoft.com/en-us/library/windows/desktop/ms684914(v=vs.85).aspx</a> provide some insight into why pulse-style semantics cannot reliably be achieved with an event object. (Basically, the kernel sometimes takes threads that are waiting for an event off its wait list temporarily, so it's always possible that a thread will miss a 'pulse' on an event. That's true whether you use <code>PulseEvent</code> or you try to do it yourself by setting and resetting the event.)</p> <p>The intended semantics of <code>ManualResetEvent</code> is that it acts as a gate. The gate is open when you set it, and is closed when you reset it. If you open a gate and then quickly close it before anyone had a chance to get through the gate, you shouldn't be surprised if everyone is still on the wrong side of the gate. Only those who were alert enough to get through the gate while you held it open will get through. That's how it's meant to work, so that's why you're seeing what you see.</p> <p>In particular the semantics of <code>Set</code> are very much <strong>not</strong> "open gate, and ensure all waiting threads are through the gate". (And if it were to mean that, it's not obvious what the kernel should do with multi-object waits.) So this is not a "problem" in the sense that the event isn't meant to be used the way you're trying to use it, so it's functioning correctly. But it is a problem in the sense that you won't be able to use this to get the effect you're looking for. (It's a useful primitive, it's just not useful for what you're trying to do. I tend to use <code>ManualResetEvent</code> exclusively for gates that are initially closed, and which get opened exactly once, and never get closed again.)</p> <p>So you probably need to consider some of the other synchronization primitives.</p>
    singulars
    1. This table or related slice is empty.
    1. POManualResetEventSlim: Calling .Set() followed immediately by .Reset() doesn't release *any* waiting threads
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USIan Griffiths
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POManualResetEventSlim: Calling .Set() followed immediately by .Reset() doesn't release *any* waiting threads
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI'm using Monitor.PulseAll() in my actual code btw. The documentation for ManualResetEventSlim.Set() says: *"Sets the state of the event to signaled, which allows **one or more** threads waiting on the event to proceed"* which, on the face of it it, is just wrong. It should say *zero or more*.
      singulars
      1. PO
      1. USMatthew Watson
    2. COThe use of 'any' in the MSDN documentation can be interpreted as making a distinction between MRE and ARE. If 40 threads are queued on an MRE, signaling it should make all 40 ready. If it does not, it's broken.
      singulars
      1. PO
      1. USMartin James
    3. COI guess the answer is "It doesn't work because it wasn't designed to work that way, and the Microsoft documentation for ManualResetEvent.Set() is incorrect and incomplete".
      singulars
      1. PO
      1. USMatthew Watson
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload