Ramps up MacPro fans and energy impact, and pegs %CPU at 100%

[newkton1]

First, thanks for this app.

I've been testing filewatcher on an 8-core MacPro running Mojave 10.14. Although it does what you say, it causes the fans to ramp-up from inaudible to very audible and the Energy Impact index shown in Activity Monitor rises to 99 which is more than the impact of running Office applications!
The %CPU is also pegged at 100% compared to about 38% when working on a Word document.
I can't imagine the code is very heavy so do you have any idea why filewatcher is being so demanding of CPU time and energy?
Could the code be cleaned-up or might there be a problem with Mojave?

Hi, this is strange. I do not have a Mac with Mojave right now, I will be able to check it in few days and look further to this :)