Naatan
commented
5 years ago I feel like you might plainly be throwing too much at the IDE to handle here. No doubt we can optimize things further, but at a certain point we will say "this is just unrealistic, please scope down your project".
All of this is to say, can you point Komodo at JUST the file you're actually working with? I feel often people just point their IDE at a top level folder and go to work. This is basically telling Komodo "I am working with ALL THE FILES that I'm currently pointing you at (ie. the top level of your project). A better way to approach this is to point it just at the specific files you're working with OR by adding excludes to your project configuration, which tells Komodo "Don't worry about these files". Your vendor folder would generally be a good one to add to your excludes.
Does this sound reasonable, or would you say that the amount of files you're pointing Komodo at is not that large? Any context you could give us on the project you're working on?
ssigwart
th3coop
Short Summary
On MacOS, Komodo gets excessively laggy when typing, scrolling, or clicking in the UI. At times, I can type up to 4 or 5 words of a sentence before the characters start displaying. In general, Komodo seems to use a lot of CPU, but at times, things seem to hang and a Python process with use 100% for a while. Also, #3639 is an issue for me on Komodo IDE too.
Steps to Reproduce
I think you'll need to use a fairly large project and work on it for a fair amount of time. Sometimes, there are issues within a few minutes. Other times, it can be around an hour or more.
Expected results
Actual results
Platform Information
Additional Information
I tried various configurations of the Code Intelligence settings. Below are my findings:
I noticed a few times that the Symbol Browser would hang showing the loading icon. This coincided with Python using 100% CPU many of the times I saw it. I'm not sure if it was every time Python used 100% or just a side effect.
When closing the app, it seems to take around 5 - 10 seconds for the app to show as closed in the macOS dock.
Settings Corresponding with the Logs Shown Below
I feel like this issue may be related to CodeIntel. Currently,
codeintel3.dbis 116MB. Incodeintel3.log, I noticed the below logged a lot. Manually running this query, there are ~3,500 results.Also, codeintel seems to be killed and restarted a lot:
Here is the output of pystderr.log.
I also have Activity Monitor samples of the Python process at 2 different times when it was at 100% CPU. I can send them if you need them.
I tried to add as much info as I could. Hopefully this is helpful. Please let me know if you need any more information.