[
https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vishal Sharda updated DISPATCH-337:
-----------------------------------
Attachment: Subsequent_memory_increase.png
Rapid_perm_memory_increase.png
Two files attached: Rapid_perm_memory_increase.png and
Subsequent_memory_increase.png
We ran two interconnected routers having 2-way SSL connection between them and
accepting 2-way SSL connections from clients. We connected several senders to
one router and several receivers to the other. Total of 250K messages were
sent from one end to the other. We saw rapid increase in memory usage of both
the routers. This memory never became low again and a subsequent identical run
increased the memory further.
Since the routers are never intended to be terminated, such memory leaks on all
subsequent connections and data transfers will eventually lead to routers being
killed.
> Huge memory leaks in Qpid Dispatch router
> -----------------------------------------
>
> Key: DISPATCH-337
> URL: https://issues.apache.org/jira/browse/DISPATCH-337
> Project: Qpid Dispatch
> Issue Type: Bug
> Affects Versions: 0.6.0
> Environment: Debian 8.3, Apache Qpid Proton 0.12.2 for drivers and
> dependencies, Hardware: 2 CPUs, 15 GB RAM, 60 GB HDD on 2 separate machines
> Reporter: Vishal Sharda
> Priority: Critical
> Attachments: Rapid_perm_memory_increase.png,
> Subsequent_memory_increase.png, config1.conf, config2.conf,
> val2_receiver.txt, val2_sender.txt
>
>
> Valgrind shows huge memory leaks while running 2 interconnected routers with
> 2 parallel senders connected to the one router and 2 parallel receivers
> connected to the other router.
> The CRYPTO leak that is coming from Qpid Proton 0.12.2 is already fixed here:
> https://issues.apache.org/jira/browse/PROTON-1115
> However, the rest of the leaks are from qdrouterd.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
