-
Notifications
You must be signed in to change notification settings - Fork 765
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pylance analysis takes a very long time when OpenCV cv2
imported and used.
#5101
Labels
needs repro
Issue has not been reproduced yet
waiting for user response
Requires more information from user
Comments
LogsWith cv2 imported: 120 seconds Long operation happens at `13:53:47.790` in the logs.
With cv2 import commented out: 2 seconds
|
I've been unable to reproduce any perf issues with this code. We'll need a complete repro case to investigate this. |
This issue has been closed automatically because it needs more information and has not had recent activity. If the issue still persists, please reopen with the information requested. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
needs repro
Issue has not been reproduced yet
waiting for user response
Requires more information from user
Environment data
Code Snippet
I can't share all my code as it's private, and it's hard to replicate as I think the length of the code has an effect. The below example is an idea of what the code looks like.
Libraries:
Expected behavior
VSCode Pylance file analysis is quick (i.e. <1s), as it happens on any file save.
Actual behavior
Analysis time can vary dramatically, generally fairly long (>5s) and occasionally very long (60s, 5 minutes, one occurence was 8888610ms, or 2.5 hours after I left my computer idle).
CPU is high while this is happening (100% on one core)
Logs in reply due to character limit
The text was updated successfully, but these errors were encountered: