Background

The mutex prevents multiple instances of the client in an effective way, allowing simple termination of any additional clients that are (attempted to be) initialized under the same mutex.

Behavior Expected

1. Client user initializes a client program. 2. Client user attempts to initialize an additional client program though one client program has already been initialized under the same mutex. 3. Client user's additional client programs do not initialize; since one is already running, the additional client programs kill themselves.

Actual Behavior

1. Client user initializes a client program. 2. Client user attempts to initialize an additional client program though one client program has already been initialized under the same mutex. 3. Client user's additional client programs do not initialize; since one is already running, the additional client programs kill themselves. 4. ISSUE Client user's first client stops working (with a popup of the Windows message indicating a crashed application).

Originally created by @yankejustin on GitHub (May 23, 2015). Original GitHub issue: https://github.com/quasar/Quasar/issues/170 <h1>Background</h1> The mutex prevents multiple instances of the client in an effective way, allowing simple termination of any additional clients that are (attempted to be) initialized under the same mutex. <h1>Behavior Expected</h1> 1. Client user initializes a client program. 2. Client user attempts to initialize an additional client program though one client program has already been initialized under the same mutex. 3. Client user's additional client programs do not initialize; since one is already running, the additional client programs kill themselves. <h1>Actual Behavior</h1> 1. Client user initializes a client program. 2. Client user attempts to initialize an additional client program though one client program has already been initialized under the same mutex. 3. Client user's additional client programs do not initialize; since one is already running, the additional client programs kill themselves. 4. <i><b>ISSUE</b></i>    <b>Client user's first client stops working (with a popup of the Windows message indicating a crashed application).</b>

kerem

2026-02-27 15:48:37 +03:00

closed this issue
added the
cant-reproduce
label

kerem commented

2026-02-27 15:48:38 +03:00

Author

Owner

@MaxXor commented on GitHub (May 23, 2015):

Again, the client application does not crash in Release mode, using the same mutex when one client is already installed. The client checks if the mutex is already initialized and then exits if it's already there.

@MaxXor commented on GitHub (May 23, 2015): Again, the client application does not crash in Release mode, using the same mutex when one client is already installed. The client checks if the mutex is already initialized and then exits if it's already there.

kerem commented

2026-02-27 15:48:38 +03:00

Author

Owner

@yankejustin commented on GitHub (May 23, 2015):

I will investigate these two issues tonight and see why my client is doing this. I will re-open if I still experience issues and will inform you of any irregularities.

@yankejustin commented on GitHub (May 23, 2015): I will investigate these two issues tonight and see why my client is doing this. I will re-open if I still experience issues and will inform you of any irregularities.

kerem commented

2026-02-27 15:48:38 +03:00

Author

Owner

@rabbitsmith commented on GitHub (May 25, 2015):

was the problem solved.

@rabbitsmith commented on GitHub (May 25, 2015): was the problem solved.

Rows
Columns

[GH-ISSUE #170] Mutex Murder #75

Background

Behavior Expected

Actual Behavior