-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Watcher is quite slow to recognize changes after recent watcher updates. #2208
Comments
What version are you comparing to when you found it fast? |
@nschonni 4.5.2 is last one but maybe 4.7.1 or 4.7.0. Here is a profile of what I am talking about. It looks like |
I doubt it's due to the Mac OS high sierra version? |
Correct, confirmed on earlier OS’ within our org.
…On Mon, Feb 26, 2018 at 5:43 PM weichenghsu ***@***.***> wrote:
I doubt it's due to the Mac OS high sierra version?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#2208 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAt_eW1UpGMUfPu7JPm7pX8IfS6WBKYBks5tYzN8gaJpZM4RYKKi>
.
|
Thanks~ Any workaround solution so far? |
I have the same problem with macOS 10.13.3. The watcher is stuck at 100% CPU usage after updating a sass file that is watched by node-sass. It then takes around 20-30s to recognize the change. Last working version for me is node-sass
|
Super slow on high sierra only. Also happens at sass (ruby gem) I believe they are sharing the same system library and the sys lib might be the bottleneck. node --version && npm --version (git)-[develop] |
Also seeing 100% cpu use on Mac OS 10.13.6. Reverting to node-sass v4.5.3 resolves it. |
I'm also experiencing this issue, node-sass is at 4.12 |
Watcher is quite slow to recognize changes after recent watcher updates. Perhaps this is isolated to large sass codebases. What used to be instant now takes 5 to 10 seconds. Once changes are recognized, compilation is normal/fast.
5.6.0
8.9.4
darwin
x64
The text was updated successfully, but these errors were encountered: