First time here? Check out the FAQ!

Wing not responsive for first few minutes of use

the last few releases i have noticed wing7 pro UI is very slow, with high latency responding to KB events for quite awhile after starting wingpro or after opening a new project.

it seems sometimes wingpro is analyzing things, based on status in the footer.

i run wingpro on debian linux, two different dev machines, both have this issue. it didnt used to be this way. my dev machine is 4 core 16GB, neither memory or cpu are anywhere near full utilization - so seems this is some threading/locking issue with wingpro?

has anyone else noticed this issue? thanks.

pymike's avatar
asked 2021-07-24 11:53:46 -0500
Wingware Support's avatar
Wingware Support
updated 2021-08-02 09:14:26 -0500
edit flag offensive 0 remove flag close merge delete


Try collecting a profile as follows:

(1) Use Edit -> Command By Name and enter: internal-profile-start,(2) Use Wing and do something that consumes CPU, (3) Use Edit -> Command By Name and enter: internal-profile-stop, (4) Then submit a bug report from Wing's help menu and check the box to include the error log (or email us the last part of the ide.log file from the settings directory listed in Wing's About box)

Thanks for reporting this issue.

Wingware Support's avatar Wingware Support (2021-07-25 08:37:01 -0500) edit

Also worth checking is whether increasing the Source Analysis > Max Cache Size preference helps since it sounds a bit like analysis is thrashing.

Wingware Support's avatar Wingware Support (2021-07-25 08:40:04 -0500) edit

thanks for the responses, I increased Max Cache Size from 2GB to 4GB, still see the unresponsive UI. Will collect a profile and send it along.

pymike's avatar pymike (2021-07-25 12:32:43 -0500) edit

submitted a bug report per your instructions, thanks!

pymike's avatar pymike (2021-07-25 14:02:22 -0500) edit

Are the source files and your home directory on a local disk? I notice more time than usual is being spent reading files and reading/writing the cache database.

Wingware Support's avatar Wingware Support (2021-07-26 16:20:08 -0500) edit
add a comment see more comments

2 Answers


By checking ide.log I was able to pinpoint a slowness in scanning the cu2qu library. I issued a pip uninstall cu2qu and now WingIde initializes faster.

Joril's avatar
answered 2021-10-07 01:48:08 -0500
edit flag offensive 0 remove flag delete link


For the record: not as fast as I'd like, but faster than before :)

Joril's avatar Joril (2021-10-08 01:39:09 -0500) edit

FWIW I don't see any problems scanning cu2qu so it's possible that wasn't actually it. If you still have the log entries and can send those to that might be useful.

Wingware Support's avatar Wingware Support (2021-10-08 11:10:52 -0500) edit
add a comment see more comments

I'm on Arch-Linux and see the same problem. I have many and large remote drives with symbolic links to my system that spin up when I start Wing. It seems that Wing scans the whole system and this takes minutes.

hiwi's avatar
answered 2021-07-30 04:33:09 -0500
edit flag offensive 0 remove flag delete link


Wing looks for Python in places it's usually installed and will scan the contents of your project (any files/dirs in the Project tool) and files found on the Python Path. Otherwise it should not scan everything. It may be possible to solve it by removing things from the project. That should generally contain only your own sources and not all the libraries/etc that you use, which Wing can find via the Python Path instead. Not sure if this will help. Seeing your IDE log might help; this is the file ide.log in your Settings Directory (listed in Wing's About box) or you can submit a bug report from the Help menu and include the log from there.

Wingware Support's avatar Wingware Support (2021-07-30 08:24:01 -0500) edit

Sorry, I forgot to mention that this behaviour is new in 8.0.1. In 7.2.9 the start is smooth. But I will look at the log.

hiwi's avatar hiwi (2021-07-30 09:20:26 -0500) edit

Thanks, that's useful to know.

Wingware Support's avatar Wingware Support (2021-07-30 09:23:47 -0500) edit

I checked ide.log. Wing starts within 1 second, checks all installed pythons (all system + 9 pyenv) within 1 second, after 'Scanned 17 Python installations' there's a 189 second pause with 'pypath update time = 188.2993347644806' next. These are the 3 minutes, where all symlinks are checked. There are some backup drives, which are only used for backups. What is Wing checking there? I hope, I don't have to analyze my network for some weird traffic.

hiwi's avatar hiwi (2021-07-30 13:14:02 -0500) edit

Are directories on the Python Path on those external drives? You can see the effective Python Path in the Source > Show Python Environment dialog or type 'import sys; sys.path' in the integrated Python Shell. It does sound like the issue is in scanning the Python Path directories, although it should really only look in those directories and not all over the place. It may look in unexpected places if it encounters symlinks to other areas, but I think that's about it. What it's doing is trying to find everything importable so it can analyse those files in order to provide auto-completion after 'import' and so it can do find uses, etc.

Wingware Support's avatar Wingware Support (2021-07-30 13:52:14 -0500) edit
add a comment see more comments

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account. This space is reserved only for answers. If you would like to engage in a discussion, please instead post a comment under the question or an answer that you would like to discuss.

Add Answer