View Issue Details

IDProjectCategoryView StatusLast Update
0021818MMW 5Otherpublic2025-12-04 23:37
Reporterlowlander Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status assignedResolutionreopened 
Product Version2024.2 
Target Version2024.2Fixed in Version2024.2 
Summary0021818: Multiple Instances won't load [Regression 3171]
DescriptionBuild 3171 won't allow multiple instances of itself, other versions (3167/4) were able to be run when 3171 was running.

3167 did allow multiple instances of itself.
Steps To Reproduce1 Disable Allow just one instance of MediaMonkey
2 Restart MediaMonkey
3 Start MediaMonkey again
--> No second MediaMonkey window loads, Task Manager does show 2 MediaMonkey.exe instances at this point.
Additional Informationhttps://www.mediamonkey.com/forum/viewtopic.php?t=108654
TagsNo tags attached.
Fixed in build3173

Relationships

related to 0021491 closedpetr MediaMonkey fails to launch on some systems (regression) 
related to 0021849 closedpetr MediaMonkey may stop responding after using the Munimize to Tray shortcut 

Activities

Ludek

2025-10-20 10:27

developer   ~0079862

Last edited: 2025-10-20 10:32

3170 works fine while 3171 fails to run multiple instances..

Related to fix of 0021491 -- so assigned to Petr to look into it..

petr

2025-10-20 11:24

developer   ~0079863

Fixed

lowlander

2025-10-23 18:44

developer   ~0079901

Verified on 3172 multiple instances of the same 3172 were able to run.

However closing 1 instances (File > Exit) closes all instances of MediaMonkey.

rusty

2025-10-23 19:39

administrator   ~0079904

Last edited: 2025-10-24 15:55

Not sure if this is relevant, but with build 3171, if 'Allow just one instance of MediaMonkey' is disabled, then occasionally after the PC goes to sleep:
- On resume, MM was minimized to the system tray (and didn't appear in the taskbar)
- On maximizing MM from the taskbar, the UI would not respond (as if there was something in focus in back of the UI like 0017431).
I haven't had a chance to look into this, and assumed that it was related to whatever caused this issue, but am noting it here in case it's relevant.

EDIT: I haven't been able to replicate this with 3172 so far.

petr

2025-10-28 16:32

developer   ~0079917

Fixed

lowlander

2025-10-30 21:32

developer   ~0079944

Verified closing via File > Exit works on 3173.

lowlander

2025-12-04 23:15

developer   ~0080137

Last edited: 2025-12-04 23:25

1. On 3179 a second instance with setting to allow 1 instance will close the first instance (separate install without only 1 instance allowed). (logged)
 1 Instance 1, allow 1 instance disabled; Instance 2, allow 1 instance enabled (both instances are separate installs)
 2 Start instance 1
 3 Start instance 2
 --> Instance 1 is closed, instance 2 is started
MediaMonkey should either
 A) Ignore 1 instance setting as they're two separate installs (ideal as 1 instance pertains to an specific install)
 B) warn user that instance 1 needs to be closed for instance 2 to run (and offer option to close instance 1 or keep using it)

2. On 3179 the second instance closes the first and second instance if you change enable the allow 1 instance on instance 2. (logged)
 1 Instance 1, allow 1 instance disabled, instance 2 allow 1 instance disabled (both instances are separate installs)
 2 Start instance 1
 3 Start instance 2
 --> Both instances run as expected
 4 On instance 2 enable allow 1 instance
 5 File > Exit on instance 2
 --> Both instances close, expect only instance 2 to close (the setting should not affect what is closed)


Note, that installing MediaMonkey runs into a similar issue where MediaMonkey is closed even if the user intents to do a separate install/update another install than the one currently running.