|
Along the same lines....yesterday I installed a second instance of fldigi onto my Windows 10 machine.? I now have one instance (original) working with my TS590SG using Rig CAT XML file and the second instance for my ICOM 9700 using flRIG.? I only want to run one at a time. When I double click on the new second instance, it does not launch right away.? When I double click again, it launches but eventually two versions show up, and one does not close on closing the window.? I kill the task via Windows 10.
?
But, on the second instance, if I right click on the icon (instead of a double click), and then select open, it launches OK, runs OK, and closes OK.
?
Just some data for the heap, LOL.
?
Joe, K1YOW
?
-------------------- From: "Jack Spitznagel (KD4IZ)" <kd4iz@...> Reply-To: <[email protected]> To: <[email protected]> Sent: February 22, 2025 at 10:46 AM EST Subject: [winfldigi] Potential Bug? fldigi instances not closing out in Windows Mostly addressed to Dave (W1HKJ) but also looking for others experiences:
?
Scenario:
I am now running current alphas of fldigi and flrig (autostarted) on a gamer Win11 workstation, but have seen this issue? going back several "final" releases and on a Win10 workstation. I use multiple instances of fldigi talking to a single instance of flrig because flrig can do KISS protocol and can control a single rig for multiple instances of fldigi looking at that rigs sound CODEC stream.
?
Before the "frequent commentators" ask, I have had poor luck setting up the other rig control engine because they either did not work at all for my use case or were a mess to configure. I have seen the problem with the other control engines. I will be using flrig.
?
I can start a single instance of fldigi with flrig and they will close out normally most always. The trouble does start after long (days) running the apps.
?
When two or more instances are running with or without flrig, I can almost always shut down the second instances, but the primary instance will shut down (autostarted) flrig but then hang and require one the "messy exit" routines to kill the hung process. This problem happens very often as quickly as 15 minutes or less after the programs are started.
?
Quite a while ago I tried capturing the hang event unsuccessfully - probably because the hang suspended the debug logging writes?
?
@Dave: What is best way to log this event when it happens?
?
@All: have you seen this same scenario when running multiple instances of fldigi either with separate instances of flrig (as in for two different radios) or a single instance of flrig hosting multiple instances of fldigi?
?
Jack Spitznagel
KD4IZ - FM19OO
Parkton, MD |
