You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 26, 2019. It is now read-only.
Another theory is that the setInterval stop working when a laptop is asleep, and upon waking catch up by calling the method x number of times, which slows it down. This could be tested by sleeping the computer and, upon waking it, try and use zazu.
We could fix this by adding debouncing on top of the setinterval.
Or I my hunch if totally off and we should look into other issues.
The text was updated successfully, but these errors were encountered:
I've noticed every now and then zazu runs slow. My theory is that this is based on the file finder locking the thread.
If this is the case we could test it by changing the interval to 0 and seeing it be laggy all the time.
This could be fixed by using child_process.fork
Another theory is that the setInterval stop working when a laptop is asleep, and upon waking catch up by calling the method x number of times, which slows it down. This could be tested by sleeping the computer and, upon waking it, try and use zazu.
We could fix this by adding debouncing on top of the setinterval.
Or I my hunch if totally off and we should look into other issues.
The text was updated successfully, but these errors were encountered: