Open MostHated opened 4 years ago
Hmm. #75 should have fixed this, if it's what I'm thinking. Can you reproduce the issue, and check the memory/CPU usage, then report back here?
Sure thing, at least, I can give it a try. I will open a window and let it be for a few hours to see if that does the trick. Though, looking at the issue you linked, I can't say that I recall it taking excessive or even a noteworthy amount of resources. I am fairly sure it would have caught my attention, but I could very well have missed it. I will definitely try and make note of the consumption at the time, though.
Thanks, -MH
Sorry for the delay. I was only just now finally able to get something solid to show. I had attempted to do some updates, but then went on to do other things and remembered a few hours later and came back to the window, you can see the results here: The first few seconds I am trying to type, hit enter, ctrl + C, etc.
Hey there, I just wanted to report that on more than one occasion, leaving FluentTerminal opened and simply idle at a prompt (so far it was been Powershell 7.0.3 each time) for an extended period of time (it was anywhere from a few hours last time to having it open overnight and throughout the next day, possibly a few days, and then anywhere in between), it becomes completely unresponsive. The main window looks like it should be fine, but no buttons respond (not even the X for close). I have to go into the task manager and force it closed.
Thanks, -MH
System Details
``` OS: Windows 10 Pro x86_64 Host: Gigabyte Technology Co., Ltd. X570 AORUS ELITE Kernel: 10.0.19041 Uptime: 5 hours, 43 mins Packages: 16 (scoop) Shell: bash 4.4.23 Resolution: 2560x1080 DE: Aero WM: Explorer WM Theme: Roamed Terminal: FluentTerminal CPU: AMD Ryzen 9 3950X (32) @ 3.500GHz GPU: spacedesk Graphics Adapter NVIDIA GeForce RTX 2070 Memory: 26814MiB / 65483MiB ```