Skip to content
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

[UWP] Visual Studio development experience: high CPU usage and Intellisense unresponsive #13214

Open
toburger opened this issue May 31, 2022 · 5 comments
Labels
Area-VS VS support for F# not covered elsewhere Bug Needs-Confirmation
Milestone

Comments

@toburger
Copy link

toburger commented May 31, 2022

When I add a UWP reference to a .NET 6.0 project Visual Studio gets very slow and uses all my CPUs.

Repro steps

I've started a hobby project to control my standing desk via Bluetooth. The source can be found here: https://github.com/toburger/IdasenDesk
In order to work with Bluetooth I need to access the Windows.Devices.Bluetooth namespace, which is part of the Universal Windows Platform (UWP).

When I open the project in Visual Studio and start to edit the code Visual Studio eats all of my CPU and Intellisense gets unresponsive.

Expected behavior

"Normal" Visual Studio development experience.

Actual behavior

Intellisense gets unresponsive after editing code unless I rest for a while and let Visual Studio catch up.

Known workarounds

Just be patient. 😉

Related information

Provide any related information (optional):

  • Operating system: Windows 11
  • .NET Runtime kind (.NET Core, .NET Framework, Mono): .NET 6.0
  • Editing Tools (e.g. Visual Studio Version, Visual Studio): Visual Studio 2022
@toburger toburger added the Bug label May 31, 2022
@toburger toburger changed the title UWP Visual Studio development experience: high CPU usage and Intellisense unresponsive [UWP] Visual Studio development experience: high CPU usage and Intellisense unresponsive May 31, 2022
@vzarytovskii
Copy link
Member

Will check it tomorrow on latest 2022 + do some profiling.

@dsyme
Copy link
Contributor

dsyme commented Sep 21, 2022

@vzarytovskii Did you do a check on this?

@dsyme dsyme added the Area-VS VS support for F# not covered elsewhere label Sep 21, 2022
@vzarytovskii
Copy link
Member

I think I did, and couldn't reproduce it on the main. Will re-check on latest 17.4.

@vzarytovskii
Copy link
Member

Checked on today's build, it seems that all works fine.
@toburger have you tested it on the 17.4 preview by any chance?

@vzarytovskii
Copy link
Member

@toburger I can't reproduce it on the 2022, is it still a problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-VS VS support for F# not covered elsewhere Bug Needs-Confirmation
Projects
Status: New
Development

No branches or pull requests

3 participants