by Barry4679 » Tue Jan 22, 2019 7:49 am
It happened again.
The exposure is when MM5 is closing down. It seems to take a long time. Maybe caused by your debug version? ... It seems during this close down, your check against multiple invocations is not working.
While testing MM5 I sometimes close MM5, and them immediately restart it. I do this to trigger MM to persist config changes, just in case MM abends during my testing.
If you close MM5, and then immediately double click the shortcut to restart it ... and think that you stumbled the double click, so you double click again ... you can get two invocations, even though AlllowJustOneVersion is checked.
nb. AlllowJustOneVersion was checked the whole time ... ie. it was not the setting that I was trying to persist.
It happened again.
The exposure is when MM5 is closing down. It seems to take a long time. Maybe caused by your debug version? ... It seems during this close down, your check against multiple invocations is not working.
While testing MM5 I sometimes close MM5, and them immediately restart it. I do this to trigger MM to persist config changes, just in case MM abends during my testing.
If you close MM5, and then immediately double click the shortcut to restart it ... and think that you stumbled the double click, so you double click again ... you can get two invocations, even though AlllowJustOneVersion is checked.
nb. AlllowJustOneVersion was checked the whole time ... ie. it was not the setting that I was trying to persist.