Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
0.18
-
None
-
Windows messaging client
Description
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.
Attachments
Attachments
Issue Links
- duplicates
-
QPID-2166 Memory leak in C++ Windows client - AsynchConnector
- Closed