Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG | memleak #391

Open
spirillen opened this issue Oct 6, 2024 · 4 comments
Open

BUG | memleak #391

spirillen opened this issue Oct 6, 2024 · 4 comments
Assignees
Labels

Comments

@spirillen
Copy link
Contributor

What is the problem you are experiencing?

Was trying to report this as Report a security vulnerability

but all I got is this

image

For the first time in years, I see what appears to be a memory leak, but as the system was completely unresponsive, and can't do much more than sharing a screenshot of the memory usage for until I had to increase the amount of RAM assigned to the mashine

image

How can we reproduce the problem?

To reproduce the problem:

  1. install the ProxMox virtual machine https://github.com/if-you-want-peace-prepare-for-war/proxmox/blob/master/ct/pyfunceble.sh (Not fully up to date with running version)
  2. run the command pyfunceble -c --preload --all --execution --hierarchical -f https://raw.githubusercontent.com/mypdns/matrix/refs/heads/master/source/porn_filters/explicit_content/wildcard.list
  3. Wait over the night, and this is the result.
  4. PS: the --preload are extremely slow to write in to the DB, only about 12 records per seconds, should be more like 1000-3000 depending on methods (PostgreSQL)

Do you have a screenshot?

Screenshot

image

What did you expect to happen?

Not using more than 100 mb of RAM

Is there a workaround?

Not that I've found

How did you configure PyFunceble?

cli_testing:
  inactive_db: yes
  whois_db: yes
  db_type: postgresql
lookup:
  dns: yes
  http_status_code: yes
  netinfo: yes
  special: yes
  whois: yes
  reputation: no
  platform: yes
  timeout: 2
dns:
  follow_server_order: no
  trust_server: yes
  server:
    - 9.9.9.10
    - 149.112.112.10
  protocol: UDP
  delay: 0.0

verify_ssl_certificate: no
max_http_retries: 2

platform:
  push: yes
  preferred_status_origin: recommended
  checker_priority:
    - availability
    - syntax
  checker_exclude:
    - reputation

Which Operating System did you use?

Ubuntu 24.04 LTS

Which Python Version did you use?

3.11

Which PyFunceble Version did you use?

4.3.0a4.dev

Additional context

I would like to add...

@spirillen
Copy link
Contributor Author

Reproduced...

image

@spirillen
Copy link
Contributor Author

It is easy to see when PyF are running both standard tests + platform

image

@spirillen
Copy link
Contributor Author

This is interesting... it seems like the memleak is related to the PostdreSQL. In the following screenshot I have solely been using MariaDB

image

@funilrys
Copy link
Owner

@funilrys funilrys moved this from 🆕 New to 📋 Backlog in PyFunceble Backlog Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 📋 Backlog
Development

No branches or pull requests

2 participants