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

Extension often fails to respond for periods of time #92

Open
Azmaeus opened this issue Jan 4, 2024 · 5 comments
Open

Extension often fails to respond for periods of time #92

Azmaeus opened this issue Jan 4, 2024 · 5 comments

Comments

@Azmaeus
Copy link

Azmaeus commented Jan 4, 2024

Installed product versions

  • Visual Studio: Professional 2022 Preview (17.9.0 Preview 2.0)
  • This extension: 1.14.11

Description

I haven't determined any cause, just randomly I'll get notified by a brown bar across the top of Visual Studio that "Visual Studio stopped responding for [n] seconds. Disabling the extension Web Compiler 2022+ 1.14.11 might help." I don't know if it's related or not, but on rare occasion the IDE will actually become unresponsive for me and I have to close it. When I get the message above I usually don't even notice. The [n] time ranges, usually it's between 5 and 30 seconds, but has on occasion been over a minute.

Steps to recreate

  1. I have not determined steps to recreate this, it simply happens at least once or twice a day

Current behavior

The extension becomes unresponsive causing Visual Studio to report it to me.

Expected behavior

The extension should work without becoming unresponsive.

@failwyn
Copy link
Owner

failwyn commented Feb 28, 2024

I'm not sure there is anything that can be done about this, I get the same reports about most of the extensions I use, most often ReSharper.

@josh-bonner
Copy link

I've also seen this version of the extension hang for as long as 90 seconds. The trigger condition seems to be when you do something that adds a file to a project with WebCompiler's "compile on build" setting enabled, such as creating a file in Solution Explorer or using the Move Type To File refactor. The hang doesn't happen when compile on build is disabled.

During builds with the setting enabled, the extension aggressively recompiles all SCSS even if there are no changed files, adding about the same amount of time to the build as the hang takes. Maybe there's something wrong with the change detection and file adds are inadvertently causing a full synchronous recompile?

@failwyn
Copy link
Owner

failwyn commented May 1, 2024

@josh-bonner That's an interesting observation, I never have compile on build enabled, which is probably why I have never seen this issue. I'll see if I can replicate it now. When you say adding a file in solution explorer, are you adding an SCSS file or is it with any file type?

@josh-bonner
Copy link

Any file type, Razor views and javascript for instance. I hadn't noticed before, but it looks like it also happens when you move or delete a file, so maybe it just triggers on any project change?

@failwyn
Copy link
Owner

failwyn commented May 1, 2024

Thanks, I'll take a look at this as soon as I can; I'm currently working on a few issues that have been reported with NUglify, then I'll take a look at this, then I'll get new version published. Work has been a bit crazy, so I haven't had the time to give these projects the attention they deserve; but I'm starting to find time here and there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants