node-notifier icon indicating copy to clipboard operation
node-notifier copied to clipboard

usernoted instability on Mac (Sierra)

Open nothingismagick opened this issue 6 years ago • 3 comments

We are noticing that in some cases, our use of node-notifier is hammering usernoted - to the point of system instability, ram bloat and eventually swapfile usage.

https://github.com/quasarframework/quasar-cli/issues/97

nothingismagick avatar Apr 12 '18 12:04 nothingismagick

I am seeing this too, but I'm not familiar enough with macOS to know how to debug. What can I do to help?

jocull avatar Jul 24 '19 00:07 jocull

Hmmm, following the comment trail linked above I was able to see that using wait: true does not cause this behavior.

It's worth noting that I had my timeouts set to 18 hours (only 64,800,000 milliseconds 😜 ) - I wanted the notifications to stick around on macOS until manually dismissed from the notification center.

It must do a busy loop on the wait time or something insane in usernoted, because with maybe 10 notifications all ticking down it was shooting one CPU core up to 100%. Once I dismiss them from the notification center the usage drops back down to normal.

jocull avatar Jul 24 '19 00:07 jocull

Can confirm - behavior is "ok" (not great) if the timeout is short. CPU is still going to jump, but it will return to normal once the time expires and the notifications remove themselves from the notification center.

Lastly, I am on macOS Mojave (10.14.5) so this is not a resolved issue still.

jocull avatar Jul 24 '19 01:07 jocull