So this has happened for a while, I use the free version so I haven’t mentioned it before.
It seems like from a user’s standpoint that Komodo is giving up CPU easily.
It runs perfectly fine until some sub-routine or update fires up, and then it slows (a lot) as the CPU is distributed, but after that is done, it (Komodo) doesn’t regain the the original processing fluidity. It happens gradually as I use the program, like a slow boil, before I realize it . The lag goes from normal (no latency) to 1-3 seconds between keypress to cursor action on the screen. And it’s intermittent, and only resolved with a reset of Komodo.
On restarting Komodo after that it often takes many minutes to restart - or I will need to click the icon repeatedly to push through the command.
If I had to guess, I would guess that the way Komodo manages it’s CPU sharing is too generously.
I use a ThinkPad, Win 10, 64Bit, 2.30GHz, RAM 8GB
It’s a nice little machine for programming.
Anyway, I have worked with Komodo for a long time, purchased previous versions, and have a love for the product and the workflow.
If there is a fix I can do, I would love to know.
If this text helps for a future version then it was definitely worth the time.
Thanks for your time.