Memory leak and hanging when using the Live Filter feature

Description

Hello - I'm encountering a memory leak that starts eating into RAM as soon as I have used the live filter feature (default shortcut f). The neovim process RAM usage starts going up and it keeps going. Before I figured what caused it, I caught it at 30 GB of RAM, after a day or so.
It also causes that particular nvim instance to become unresponsive after not too long (minutes).
This is on Windows 10. neovim usually takes about 3MB. As soon as I have used the live filter in nvim tree, the process goes to something like 12MB, and slowly rising from there. Even after you have closed/cleared the filter. Very easy to reproduce. Would be great if someone could look into it. I can provide more testing and details.
Thanks!

Neovim version

0.10.0

Operating system and version

Windows 10

Windows variant

No response

nvim-tree version

1.6.1

Clean room replication

Please see above

Steps to reproduce

Please see above

Expected behavior

Please see above

Actual behavior

Please see above

Reproduce the leak on Windows 10 with Neovim 0.10.0 and nvim-tree 1.6.1 by using the live filter with its default f shortcut, then observe memory and responsiveness after clearing the filter. Trace the live-filter implementation and identify why resources continue accumulating; done means memory remains stable and the nvim instance stays responsive after filtering ends.