I’m noticing a huge memory consumption of the
overwolf.io.listenOnFile API when used on big files, even when a void handler is passed to the API.
To reproduce the issue:
- Download the debug apk from there
- Launch Hearthstone
- Download the log file from there
- Copy it to the Hearthstone/Logs folder
- Open the devtools for the “Firestone - Background” window, and run
debugListenForLogs(). This will call the
overwolf.io.listenOnFileAPI on the new Power2.log file that you just copied, with an empty handler (meaning the results of the file being read in the callback will simply be ignored)
- If you look in the Task Manager, you see the memory used by the Firestone process climb quite high, and not go down even after forcing a garbage collection from the dev tools. For me, it goes from 300 MB before reading the log file to 600 MB after reading it. Also please note that the memory doesn’t go down even after waiting for a while.
It’s possible that it’s simply some memory waiting to be GCed, but I don’t know how to force the garbage collection on the API side