[zope2-tracker] [Bug 143683] Re: Leak in Session Data Container

[Tres Seaver]

In effect, this original creates a scenario which is too artificial to fit
within the framework, which is Products.Sessions -> Products.Transience ->
tempstorage:   that framework is designed to allow the application
programmer to store basically arbitrary data in the session, and to have
session data cleared out opportunisically as new values are added to the
session container over a number of requests.

Jamming in a large number of large session objects in a short period of
time, and then stopping all requests which mutate sessions to examine RAM
usage, defeats the whole design.

It is possible that recent Python versions' improvements to heap management
have also contributed to improvements here, as they allow the space which
the framework opportunistically recovers as it operates to be returned more
efficiently to the OS.


** Changed in: zope2
       Status: Confirmed => Invalid

-- 
Leak in Session Data Container
https://bugs.launchpad.net/bugs/143683
You received this bug notification because you are a member of Zope 2
Developers, which is subscribed to Zope 2.