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 2012/09/11 17:59:07 UTC
[jira] [Created] (QPID-4295) Windows client memory leak:
AsynchConnector
Chuck Rolke created QPID-4295:
---------------------------------
Summary: 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
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 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
[jira] [Updated] (QPID-4295) Windows client memory leak:
AsynchConnector
Posted by "Chuck Rolke (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/QPID-4295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chuck Rolke updated QPID-4295:
------------------------------
Attachment: AsynchConnector-leak.txt
Stack trace of allocation that is never freed.
> 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
> Attachments: AsynchConnector-leak.txt
>
>
> 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 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