Leaking HTTP requests (was: RE: [Zope] Leaking
brian at zope.com
Thu May 13 15:42:43 EDT 2004
FWIW - zope.org is suffering hugely from this as well, so
I'm following this thread eagerly ;)
Brian Lloyd brian at zope.com
V.P. Engineering 540.361.1716
Zope Corporation http://www.zope.com
> -----Original Message-----
> From: zope-bounces at zope.org [mailto:zope-bounces at zope.org]On Behalf Of
> Stefan H. Holek
> Sent: Thursday, May 13, 2004 2:37 PM
> To: Jean-Francois.Doyon at CCRS.NRCan.gc.ca
> Cc: zope at zope.org
> Subject: Re: Leaking HTTP requests (was: RE: [Zope] Leaking
> This confirms my suspicion somewhat that the global request patch is to
> blame. IIRC Localizer uses this, doesn't it?
> Do you have the possibility to test without the (monkey?) patch, or
> without Localizer entirely?
> Huima has just recently reported pretty much the same bug and he is
> using PTS, which again utilizes the global request patch (I think).
> On Donnerstag, Mai 13, 2004, at 21:31 Europe/Vienna,
> Jean-Francois.Doyon at CCRS.NRCan.gc.ca wrote:
> > Oh, wait a minute ...
> > Looks like I'm actually leaking HTTP requests!
> > Class May 12, 2004 5:08 pm May 13, 2004 3:26 pm Delta
> > Acquisition.ImplicitAcquirerWrapper 7190 138920 +131730
> > ZPublisher.HTTPRequest.HTTPRequest 352 18123 +17771
> > ZPublisher.BaseRequest.RequestContainer 329 18095 +17766
> > ZServer.HTTPResponse.ZServerHTTPResponse 338 18103 +17765
> > I saw some traffic on this same topic about archetypes & plone ...
> > Hopefully I'll be able to track this down more easily than wrapper
> > problems.
> > Still any input will be appreciated, tracking down memory leaks always
> > seems
> > like black magic to me :P
> > Thanks,
> > J.F.
> The time has come to start talking about whether the emperor is as well
> dressed as we are supposed to think he is. /Pete McBreen/
> Zope maillist - Zope at zope.org
> ** No cross posts or HTML encoding! **
> (Related lists -
> http://mail.zope.org/mailman/listinfo/zope-dev )
More information about the Zope