Good evening friends, I’m using ob2, downloading many hits and saving them as a file, 10kb files, but over time it only increases the memory until I restart the system, even if I stop the work it clears hits, starting again it continues with the accumulated memory, I have to restart it every time it reaches the memory limit, bots in the logs are disabled.
Sounds like a memory leak, No idea about any actual fixes. I’ll try to see if I can replicate it.
an example too, if I have 10m hits, I just open ob2 and go to hits it uses 30gb of memory, I delete all the hits and without using or starting anything it has 30gb in use, and the memory usage drops
A temporary fix I would recommend is changing the config settings to output hits to a webhook, txt file, or basically anything other than the internal Database.
It loads all the hits from the DB in memory because of bad design. In the new web client, everything is paginated so it shouldn’t happen anymore.
which new client is already available
Not available yet, I’m still developing it
So the native may have the same problem, or not? why micro for him!
Yes native works the same way sadly. I will get around to optimizations after I’m done with this rewrite.
1 Like