qpid-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kerry Bonin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (QPID-4345) Windows memory leak
Date Tue, 25 Sep 2012 19:42:07 GMT

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

Kerry Bonin updated QPID-4345:
------------------------------

    Attachment: windows_close_leak_r1390053.patch

Fix for Windows memory leak.  One of our team leads, Ben Holm, developed this fix.  It appears
to resolve the leak in small scale testing, we are about to test it in our large scale environment.
 This appears to be an improperly handled corner case, where (at least on Windows) one buffer
is leaked per connection close.  This fix hands the buffer back to a managed pool.
                
> Windows memory leak
> -------------------
>
>                 Key: QPID-4345
>                 URL: https://issues.apache.org/jira/browse/QPID-4345
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker, C++ Client
>    Affects Versions: 0.12, 0.18
>         Environment: Windows
>            Reporter: Kerry Bonin
>            Priority: Blocker
>             Fix For: 0.19
>
>         Attachments: windows_close_leak_r1390053.patch
>
>
> In our large system performance test environments we see Broker memory growth until the
process crashes.  This appears to be reproducible simply by opening and closing connections
as fast as possible.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org


Mime
View raw message