Hi Team. I have a similar experience to Anthony. With virtualization enabled and disabled (GPU), when running, one of the Teamflow tasks runs at approximately 20-40% CPU usage. It appears that this same task is the one that persists after closing the desktop application (using the Windows version).

Other than that, the app seems fantastic, but as for Anthony, on a laptop, it's a deterrant. Great to see that you are giving this some attention.

I just realized 60% of my CPU was being utilized by old instances of Teamflow that I had completely closed out of. And yet those old Teamflow processes which should have been shut down and gone have been alive and utilizing 16%+ CPU per process (3x Teamflow processes) for the last 24 hours that I thought I was offline and closed out of Teamflow. I believe some of those had been running for over a day as well. That's a big issue, especially for laptops.

Performance issues like that are pretty bad, should be fixed immediately. When a child process is terminated the parent process needs to terminate as well.