You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Vishal Sharda (JIRA)" <ji...@apache.org> on 2016/10/03 21:35:21 UTC
[jira] [Comment Edited] (DISPATCH-337) Huge memory leaks in Qpid
Dispatch router
[ https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15543002#comment-15543002 ]
Vishal Sharda edited comment on DISPATCH-337 at 10/3/16 9:34 PM:
-----------------------------------------------------------------
One router on a machine (LNP-1) in a cluster of 5 completely connected routers suddenly started growing in memory and stopped accepting incoming connections. We cannot even run qdstat on that router to know its status.
This is happening on one machine after we cherry-picked the fixes of DISPATCH-491 and DISPATCH-505 on all 5 machines in this cluster.
was (Author: vsharda):
One router on a machine (LNP-1) in a cluster of 5 completely connected routers suddenly started growing in memory and stopped accepting incoming connections. We cannot even run qdstat on that router to know its status.
> 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: LNP-1_Huge_memory.png, LNP-1_Leak_starts.png, LNP-1_not_accepting_connections.png, Memory_usage_first_run_no_SSL.png, Memory_usage_subsequent_run_no_SSL.png, Rapid_perm_memory_increase.png, Subsequent_memory_increase.png, Tim-Router-3-huge-memory-usage.png, Tim_Router_3.png, Tim_Routers_3_and_6_further_leaks.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: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org