[ 
https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15556214#comment-15556214
 ] 

Ted Ross commented on DISPATCH-337:
-----------------------------------

Did you build your executable without debug symbols?  Without them, the pstack 
isn't useful.

What is the CPU usage of the router process?  Can you get the CPU for each 
thread?

Does the memory footprint rise steadily or does it burst?  IS it somewhere in 
the 12MB per hour range?


> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to