« Last post by muse2u on September 18, 2016, 03:16:33 PM »
My primary use of Process Lasso for the last few years is as a tool to monitor the processes on my Windows 10 computer and to perform troubleshooting. The information provided by Process Lasso is far above anything else that I have seen in other task/process monitors, and has been the tool of choice in resolving many performance issues. The value in its use as a performance monitor tool is proportional to the confidence in its reported information. If the information is misleading or inaccurate, or the monitor/logging function exacerbates the problem, the program is useless as a trouble shooting tool.
I have read the forum entry several times, and since I am not as well versed in the subject as your moderators, I have only a limited understanding.
My experience with this issue is as follows:
In the last year or so, I have seen logs of the events described above with respect to Firefox. Process Lasso has log settings for process launch and terminate turned on. A launch entry is logged at Firefox start, and Firefox executes normally for some time. Something then triggers a Firefox/Process Lasso issue, that reflects, what appears as a loop in the logging process, an endless logging of process launch (with the same PID) and process terminates (with the same PID but different PID as the launch). The counter of Firefox uptime increments, suggesting that the process is still running.
In the first incarnation of this problem, the looping log entries were accompanied by a significant performance problem that was not identified by Process Lasso (i.e. according to Process Lasso responsiveness was 100% when it clearly wasn't). Terminating any Firefox processes using Process Lasso, did not clear the performance issue nor the log loop. With Firefox processes no longer in the Process Lasso task list, it was necessary to bring up the Windows Task Manager, which showed that Firefox was still executing. Terminating Firefox with the Windows Task Manager, cleared both the performance issue and the Process Lasso log loop.
In the second incarnation of this problem, a few months ago something happened to change the experience of the problem (as commented above, maybe a Windows 10 update). The Process Lasso log looping was no longer accompanied by a performance issue and, after terminating Firefox processes in Process Lasso, the Windows Task Manager failed to show any running Firefox tasks. So, as was noted above, maybe the running Firefox task was 'hidden' and could no longer be manually terminated, or the task had ended and Process Lasso logging was hung in the log loop.
In both scenarios, stopping and starting Process Lasso and the governor, had no effect on clearing the loop, only a reboot of the computer cleared the problem.
It should also be noted that while the Firefox task is up and running (before any process termination is performed manually) and the loop is being registered by Process Lasso, Firefox is useable (somewhat sluggish in scenario 1) and therefore I don't understand the conclusion that the loop is caused by a crashing process, ie. Firefox crashing.
The suggestion above that we turn off logging of process launch/terminates just hides the problem and is not a solution. The option is not selective, it prevents logging of all process launch/terminates, information that is valuable in performance identification troubleshooting. If the log loop is a figment of Process Lasso imagination or is actually caused by the running of Process Lasso, then we have a Process Lasso confidence issue. If it is reporting an actual Windows process failure, it is doing the job that I paid for.
Does anybody have any idea where in the Bitsum scheme of things, the status of the solution is? Two years is a long time between identification of a problem and a solution in a V9 version of the program!