You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Susan Hinrichs (JIRA)" <ji...@apache.org> on 2016/09/28 01:23:20 UTC

[jira] [Updated] (TS-4899) Http2ClientSession object leaks

     [ https://issues.apache.org/jira/browse/TS-4899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Susan Hinrichs updated TS-4899:
-------------------------------
    Summary: Http2ClientSession object leaks  (was: Session and Transaction objects leak)

> Http2ClientSession object leaks
> -------------------------------
>
>                 Key: TS-4899
>                 URL: https://issues.apache.org/jira/browse/TS-4899
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP, HTTP/2
>            Reporter: Susan Hinrichs
>            Assignee: Susan Hinrichs
>            Priority: Blocker
>             Fix For: 7.1.0
>
>
> Running master plus proposed fix for TS-4813 (without this fix, traffic_server crashes very quickly).  
> After a short time (10 minutes), I noticed that the process memory utilization was growing.  I took the machine out of rotation and waited for existing connections to drain.  The memory use summary from SIGUSR1 shows that many (most?) Http2ClientSession, Http2Stream, and Http1ClientSession objects are not being freed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)