-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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 causes high cpu load #278
Comments
Please attach the ritwickdey.LiveServer-unresponsive.cpuprofile.txt file. |
I think, it's because of #255 |
Please upgrade the extension to lastest version (I've updated it recently). If it doesn't work, please let me know |
If you can share reproducible steps that would be even better. |
Thanks helped! |
No, I am gettin it only on GitHub. I dont know why. Make a new folder 'mvc_sajt' in 'htdocs' and state all files from downloaded file(folder) 'mvc-master' on it. Advice for u: Use the Xampp. |
Hello Ritwick, |
It was fixed after updating to new VScode version and extension for me. |
Hello, |
Hi, |
Same issue, MacOs, latest VsCode (1.41.1) and Live Server 5.6.1 :( |
In my situation it seems to be related to having the composer "vendor" folder for my project included in my workspace. Maybe it is having to watch all of those tens of thousands of files for file refreshes? Anyway I was able to select only my main web app folder and reduced my CPU usage from ~300% to 5%. Is there some way to exclude folders from the reload rules? |
#741 |
Issue Type: Performance |
Hi, |
Hi, |
Hi Downgraded extension to V5.6.0 and still same issue. Any ideas? |
ritwickdey.LiveServer-unresponsive.cpuprofile.txt Hi, here is my device information: Edition Windows 10 Pro |
ritwickdey.LiveServer-unresponsive.cpuprofile.txt This is my device: |
Hello Ritwickdey, |
Performance
LiveServer
5.4.0
Linux x64 4.15.0-45-generic
1.31.0
/home/denis-yurkov/ritwickdey.LiveServer-unresponsive.cpuprofile.txt
Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load
The text was updated successfully, but these errors were encountered: