<!-- Read the guidelines for filing an issue first. https://github.com/microsoft/pylance-release/blob/master/TROUBLESHOOTING.md#filing-an-issue --> ## Environment data <!-- To find your version, you can either: - Open the VS Code extensions panel. Locate Pylance from the list of installed extensions. The version appears next to the name. - Select "View: Toggle Output" from the command palette (Ctrl+Shift+P on Windows/Linux, Command+Shift+P on macOS), then select "Python Language Server" in the dropdown on the right. Look for the line Pylance Language Server version X in the console. --> - Language Server version: 2022.4.3 - OS and version: macOS 12.3.1 - Python version (& distribution if applicable, e.g. Anaconda): 3.7 ## Expected behavior Not use 100% CPU ## Actual behavior Never ending 100% CPU usage ## Logs <!-- Enable trace logging by adding "python.analysis.logLevel": "Trace" to your settings.json configuration file. Adding this will cause a large amount of info to be printed to the Python output panel. This should not be left long term, as the performance impact of the logging is significant. --> ## Code Snippet / Additional information <!-- Note: If you think a GIF of what is happening would be helpful, consider tools like https://www.cockos.com/licecap/, https://github.com/phw/peek or https://www.screentogif.com/ . --> Downgrading to 2022.3.0 makes the issue go away. It comes back immediately when I switch to 2022.3.1 or later.
Environment data
Expected behavior
Not use 100% CPU
Actual behavior
Never ending 100% CPU usage
Logs
Code Snippet / Additional information
Downgrading to 2022.3.0 makes the issue go away. It comes back immediately when I switch to 2022.3.1 or later.