You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Chuck Rolke (JIRA)" <ji...@apache.org> on 2016/10/28 19:24:58 UTC
[jira] [Updated] (QPID-4295) Windows client memory leak:
AsynchConnector
[ https://issues.apache.org/jira/browse/QPID-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke updated QPID-4295:
------------------------------
Attachment: qpid-4295-fixes-windows-only.patch
This issue is a pain as there as a constant, per connection memory leak with both AMQP 0-10 and 1.0. Even today.
The patch show how to stop the leak in windows but it is a pretty bad patch otherwise.
> Windows client memory leak: AsynchConnector
> -------------------------------------------
>
> Key: QPID-4295
> URL: https://issues.apache.org/jira/browse/QPID-4295
> Project: Qpid
> Issue Type: Bug
> Components: C++ Client
> Affects Versions: 0.18
> Environment: Windows messaging client
> Reporter: Chuck Rolke
> Fix For: Future
>
> Attachments: AsynchConnector-leak.txt, qpid-4295-fixes-windows-only.patch, qpid-4296.gif
>
>
> Putting a windows messaging in a loop that does connection.open() and connection.close() without creating senders, receiver, or messages causes gradual increase in memory usage.
> Analysis reveals allocations of windows::AsynchConnector objects that are never getting deleted.
> See attachment with stack trace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org