Ticket #496 (defect)
Opened 3 years ago
Last modified 3 years ago
Memory leaks in threadlocal objects
Status: closed (fixed)
| Reported by: | fumanchu | Assigned to: | fumanchu |
|---|---|---|---|
| Priority: | high | Milestone: | 2.2-final |
| Component: | CherryPy code | Keywords: | |
| Cc: |
The threadlocal objects cherrypy.serving and cherrypy.thread_data leak, leaving at least one copy of the Request, Response, and any thread_data objects in memory per thread. While this isn't a huge problem when using the builtin server (which usually pools 10 threads), it can quickly become a problem when using WSGI gateways where thread-creation is not handled internally.
I added a new test for this in [1012], and will be adding fixes right after that. I just wanted a ticket for completeness. ;)
Change History
03/22/06 02:04:27: Modified by fumanchu
- status changed from new to closed.
- resolution set to fixed.
Fixed in [1013].