PyFunceble: Memory leak? at least a huge memory consumption
Bug description
A clear and concise description of what the bug is. I’m running this app (only) on a virtual host with 4GB, but after a while it have eaten all the memory to final fail
$ free -m
total used free shared buff/cache available
Mem: 3850 3014 326 29 509 596
Swap: 0 0 0
5 minutes later...
free -m
total used free shared buff/cache available
Mem: 3850 3097 242 29 510 513
Swap: 0 0 0
Modifications under .PyFunceble.yaml
Ask @mitchellkrogza running on his Badd-Boyz-Hosts
Reproduction
Steps to reproduce the behavior: Open source at https://github.com/spirillen/Dead-Domains
Expected behavior**
freeing memory as each query is processed and written to disk
Versions
OS: Debian 10, (Buster) Python Version: Python 3.7.3 PyFunceble Version: pyfunceble 2.2.0. (Green Galago: Skitterbug)
Additional context
None
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 21 (21 by maintainers)
Commits related to this issue
- Several code change/introduction. * Improvement of the inactive, autocontinue and mining database. Indeed, before this patch, the database were kept in memory even if we don't use them directly. ... — committed to funilrys/PyFunceble by funilrys 5 years ago
- Fix outputs of syntax test. Indeed, before this patch, it was necessary to use the `--plain` argument/config to get the plain list while testing for syntax. From now, the hosts generation is disabled... — committed to funilrys/PyFunceble by funilrys 5 years ago
Can we resume what’s working and what’s not working now that I merged the
restructuration
branch into thedev
branch?Thanks!
By the way, the SQLite db-type will be dropped in the future (already the case in the dev branch). It’s not as efficient as the
mariadb
ormysql
database types while doing some multiprocessing.