occasionally, the client (7.3.2100.0 at m1 air running macos13.3.1) fails to receive new update, which also results in com.eset.network slowly eating away all the RAM, eventually forcing me to reboot to resolve the issue.. is this something known already?