Process Lasso Log Keeps Displaying "Process Has Terminated" Over and Over

[Capt_Ahab]

Hi, I recently installed FL Studio on my PC and I have noticed that in the Process Lasso log after I close out of the FL Studio program, it will continually display the closed out process in the log with the action item being "Process Has Terminated". It will continue to do this for days at a time- referencing a process that doesn't even show up in the Windows Task Manager. The log entries only stop displaying after a reboot. Does this somehow mean that the application is still running somehow? The odd thing is that the process doesn't even show in the "All Processes" tab any longer so I'm wondering if this is some kind of bug.

[edkiefer]

Hi, Thanks for the report.

What version of PL are you running, make sure you are up to date.

[Capt_Ahab]

I'm on the latest 9.8.4.2 x64. I did click "Check For Updates" just to make sure and it says that I'm on the latest version.

Thanks!

[edkiefer]

I'm on the latest 9.8.4.2 x64. I did click "Check For Updates" just to make sure and it says that I'm on the latest version.

Thanks!

I think there is a fix in the current beta build that might fix that issue.
The current beta is very stable if you want to move to it (menu option>UPDATES>"include beta version"

I'll need to check back to confirm 100%.

[Capt_Ahab]

Okay cool! Let me know if you can confirm that the bug is fixed.

Thanks!!

[Jeremy Collake]

Yes, this problem should be fixed in the latest beta version.

Alternatively, you can mitigate it by turning off logging of process creation and termination events (see 'Options / Log settings').  [edited to include creation events]

[Capt_Ahab]

So I did the update to beta and it looks like the same thing is happening. Do I need to restart the Process Lasso service in order for it to stop showing those log entries?

Thanks!

[Capt_Ahab]

I turned off the log entry to show terminated processes just to see what would happen. It looks like I am seeing a bunch of entries as well for processes starting up but again, I don't see any evidence of this in Windows Task manager nor the "All Processes" tab.

[Jeremy Collake]

Sorry, you must turn off process creation log events as well.

Alternatively, you *might* also have luck enabling 'Options / General settings / Ignore problematic processes'.

Thank you for letting me know it is still occurring in the latest beta. We had some difficulty reliably reproducing this condition, so I was not certain of the fix. We'll make a new effort to reproduce and diagnose it prior to the next final version.

I'll post to this thread with further updates on this issue.

[Capt_Ahab]

I did try disabling problematic processes but it looks like it's still showing those programs. I'll just have to set the program not to log starting processes as well for now.

Thanks!

[Jeremy Collake]

Can you, by chance, advise any usage scenario of FL Studio where we are likely to see this effect? We are trying to reproduce it.

Thank you

[Capt_Ahab]

I'm not sure if FL Studio by itself is necessarily the issue but I believe that after adding mutiple VST plugins to the software, I started noticing the issue. Unfortunately, I'm not sure what plugin started causing the issue as I had added quite a few new VSTs in a short timespan. Hopefully that will give you something to go on. I do notice that after I close out FL Studio, the ILBridge.exe process and FL64.exe will stay in Task Manager and I will have to forcefully end the tasks. This is when Process Lasso begins to continually show that the task has been started and stopped continually in the log section of the software.

[edkiefer]

So this logging issue happens only with linked processes of FL Studio and itself?

No other windows or other programs show this issue?

[Capt_Ahab]

That's correct. I've only seen this happen so far with FL Studio and its associated processes.

[Jeremy Collake]

It sounds like FL64.exe and ILBridge.exe are stuck in some type of exception state that isn't being properly handled.

This unusual process state is confusing Process Lasso, though it doesn't have any real consequence apart from the logging.

Resolution may require some re-architecting, so the problem may continue in the next final version. However, we are tracking it, and it will get resolved in time.

Thank you for the additional information!

[Capt_Ahab]

If this is the case, it would sound like Windows isn't completely shutting down the processes either. Short of rebooting the PC, would there be a way to have the OS completely terminate the processes?

Thanks!

[Jeremy Collake]

You could maybe sign the user out, but that's not much better than a reboot. There might be something else that could be done to terminate them, but it would require researching the underlying cause of the 'hung' instances.

Can you tell me the thread count for those zombie processes? This is shown in Process Lasso, or the Task Manager Details pane if the 'Threads' column is enabled. If it happens to be 0, I may use that as a work-around.

Thanks!

[Capt_Ahab]

Hi there! I guess I will just have to restart the computer every now and then when I see those items pop up in the logs (right now I have those messages suppressed). Unfortunately, the zombie processes never show in Process Lasso after they have been terminated so there is no thread count to see. They will only show up in the logs. Hope that helps!

[Jeremy Collake]

I have now issued a new beta, v9.8.6.1, that you can try.

Since we still haven't reproduced it locally, I can't say for certain it will resolve the problem, but it seems likely that it will.

If you do try it, please let me know how it goes.

Thanks

[Capt_Ahab]

Hi there! I'm installing it now. I'll let you know if the issue continues.

Thank you!