PS Paul... Ive just had a thought.
Since your fixes, HG612stats has been running fine.. and the only problems I see now have occurred after a failed HG612_current_stats.
-----------
I dont know the internals of your program or code.. but something has just struck me.. if Im not surmising your code correctly ignore me.
- HG612stats checks for other instances and if false runs the code to collect stats.
- HG612_current_stats checks for other instances and if false.. pauses 10 seconds and then collects stats.
During this 10 seconds DSLstats could have started, causing HG612_current_stats to fail. - HG612_current_stats then gets stuck in task manager
- From my observations HG612stats always appears to get stuck when HG612_current_stats does.. and this is when all stat logging ceases... and numerous HG612stats.exe start piling up in task manager
Not quite.
If HG612_stats.exe is running & HG612_current_stats is run manually, HG612_current_stats.exe is delayed by whatever delay setting is specified via Settings Editor.
However, if HG612_current_stats.exe is triggered by the schedule set via Settings Editor or by a resync being detected whilst running HG612_stats.exe 24/7, any pre-set delays are ignored & as that check is made AFTER HG612_stats.exe has logged out of the modem & written the data to modem_stats.log, there shouldn't really be any problems.
These checks used to happen around 2 seconds into HG612_stats.exe.
With the recent additional checking & dealing with DSLStats.exe also running 24/7 etc., the checks for scheduled logging or resyncs are now made around 3 seconds into HG612_stats.exe.
Grabbing the stats for current_stats takes around 7 seconds & if auto-graphing is switched on, that adds another 4 seconds (approximately).
Adding compatibility for HG622 modems added a little more time due to needing to harvest more/different data & the whole process can now take typically around 14-15 seconds on my PC when scheduled current stats & auto-graphing are all switched on, a bit longer if DSLStats was sampling at the time HG612_stats.exe was due to start.
There did seem a strong possibility that some of this would at some stage clash with DSLStats, hence the recent extra checking that seems to work without any issues (at my end anyway).
Now that Eric has added the "Synchronise with HG612-Modem-Stats" option to v 3.92, any remaining issues will hopefully have been dealt with.
It may just have been that the timing of DSLStats's sampling clashed on your particular setup.
I suppose you'll find out at 22:00 tonight or at 06:00 tomorrow morning (if that's when harvesting/graphing current stats is scheduled on your PC).