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

Memory leak when using BuiltinSSLAdapter #647

Open
1 of 3 tasks
bmourgues opened this issue Feb 14, 2024 · 3 comments
Open
1 of 3 tasks

Memory leak when using BuiltinSSLAdapter #647

bmourgues opened this issue Feb 14, 2024 · 3 comments
Labels
bug Something is broken triage

Comments

@bmourgues
Copy link

bmourgues commented Feb 14, 2024

❓ I'm submitting a ...

  • 🐞 bug report
  • 🐣 feature request
  • ❓ question about the decisions made in the repository

🐞 Describe the bug. What is the current behavior?
When enabling ssl_adapter on WSGIServer, there is a memory leak each time a connection is received

❓ What is the motivation / use case for changing the behavior?

πŸ’‘ To Reproduce
Using example code from cheroot with added ssl_adapter allows to reproduce the bug

Steps to reproduce the behavior:

  1. Run this server:

    from cheroot.wsgi import WSGIServer
    from cheroot.server import get_ssl_adapter_class
    
    def my_crazy_app(environ, start_response):
        status = '200 OK'
        response_headers = [('Content-type','text/plain')]
        start_response(status, response_headers)
        return [b'Hello world!']
    
    addr = '0.0.0.0', 8078
    ssl_cert='/etc/shinken/certs/server.cert'
    ssl_key='/etc/shinken/certs/server.key'
    
    server = WSGIServer(addr, my_crazy_app)
    
    server.ssl_adapter = get_ssl_adapter_class()(certificate=ssl_cert, private_key=ssl_key)
    
    server.start()
  2. Make some requests: for I in $(seq 2000); do wget --quiet -O /dev/null --no-check-certificate https://localhost:8078 ; done

  3. See error: read RSS value from following command each time requests are made to server ps wu -p $(pgrep cheroot_test)
    RSS value increases and never goes down.

πŸ’‘ Expected behavior
Stable memory consumption for a server usage

πŸ“‹ Details

πŸ“‹ Environment

  • Cheroot version: 10.0.0
  • Python version: 3.11.8 / 3.11.6 / 3.11.5
  • OpenSSL version: 3.0.12 / 3.0.13
  • OS: CentOS 7 / Redhat 8.9 / Alma 8.9
  • Browser: any

πŸ“‹ Additional context

OpenSSL has been compiled from https://www.openssl.org/source/openssl-3.0.13.tar.gz without any special option (except install prefix)

Python has been compiled from source https://www.python.org/ftp/python/3.11.8/Python-3.11.8.tgz with following options

./configure --prefix=/opt/shinken/python311 --enable-optimizations --with-openssl=/opt/shinken/openssl/ --with-openssl-rpath=/opt/shinken/openssl/lib64 --with-ssl-default-suites=openssl --without-static-libpython --disable-test-modules --enable-shared LDFLAGS="-L/opt/shinken/openssl/lib64 -Wl,-rpath=/opt/shinken/python311/lib" 

If you need more information or if I can help anyway tell me

@bmourgues bmourgues added bug Something is broken triage labels Feb 14, 2024
@webknjaz
Copy link
Member

Hello. Is this reproducible with a distro-default Python in any official/public container image? I'd rather not have a repro dependent on compiling CPython from scratch.

Is there a console log output that you can share?

@bmourgues
Copy link
Author

bmourgues commented Feb 15, 2024

Hello,

you can reproduce this issue on Debian bookworm (12.5)

  • python version 3.11.2
  • cheroot version 9.0.0

I also managed to reproduce the same issue with cheroot version 10.0.0 in a virtual environment on the same system.

No log or console log, as everything works fine, but this memory leak

If needed, you can generate your certificate with following command :
openssl req -x509 -newkey rsa:2048 -nodes -keyout server.key -days 365 -out server.crt

@bmourgues
Copy link
Author

After further investigation the leak appeared in version 8.3.0
Older versions do not seem to leak.

We suspect BuiltinSSLAdapter.get_environ(self, sock) method to be the root cause.
Removing all code in this method except the first dict creation, seems to solve leak issue.

I hope this may help you to target the problem ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is broken triage
Projects
None yet
Development

No branches or pull requests

2 participants