[
https://issues.apache.org/jira/browse/DISPATCH-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514271#comment-15514271
]
Vishal Sharda commented on DISPATCH-337:
----------------------------------------
Hi Ted,
Here is the output. This router has grown to nearly 160 MB in memory.
tim@tkuchlein3-linux:~$ qdstat -m
Types
type size batch thread-max total in-threads
rebal-in rebal-out
==============================================================================================
qd_bitmask_t 24 64 128 640 192
55,913 55,920
qd_buffer_t 536 16 32 118,624 115,936
1,658,161 1,658,329
qd_composed_field_t 64 64 128 64 64 0
0
qd_composite_t 112 64 128 128 128 0
0
qd_connection_t 224 64 128 1,024 128 95
109
qd_deferred_call_t 32 64 128 64 64 0
0
qd_field_iterator_t 128 64 128 16,192 13,184
169,723 169,770
qd_hash_handle_t 16 64 128 128 128 0
0
qd_hash_item_t 32 64 128 128 128 0
0
qd_hash_segment_t 24 64 128 64 64 0
0
qd_link_t 48 64 128 1,088 128 101
116
qd_listener_t 32 64 128 64 64 0
0
qd_log_entry_t 2,104 16 32 1,008 1,008 0
0
qd_management_context_t 56 64 128 64 64 0
0
qd_message_content_t 640 16 32 26,512 26,032
102,426 102,456
qd_message_t 128 64 128 27,072 26,112
49,998 50,013
qd_node_t 56 64 128 64 64 0
0
qd_parsed_field_t 80 64 128 7,680 4,928
88,639 88,682
qd_timer_t 56 64 128 128 128 0
0
qd_work_item_t 24 64 128 1,024 128 3,059
3,073
qdpn_connector_t 600 16 32 1,024 48 428
489
qdpn_listener_t 48 64 128 64 64 0
0
qdr_action_t 160 64 128 320 128
469,489 469,492
qdr_address_config_t 56 64 128 64 64 0
0
qdr_address_t 264 16 32 64 64 0
0
qdr_connection_t 216 64 128 1,152 192 112
127
qdr_connection_work_t 56 64 128 192 128 128
129
qdr_delivery_ref_t 24 64 128 448 128
102,729 102,734
qdr_delivery_t 144 64 128 26,304 25,344 5,184
5,199
qdr_error_t 24 64 128 192 128 127
128
qdr_field_t 40 64 128 8,448 8,384 9,077
9,078
qdr_general_work_t 64 64 128 192 128
54,906 54,907
qdr_link_ref_t 24 64 128 2,176 256
259,099 259,129
qdr_link_t 264 16 32 1,072 96 457
518
qdr_node_t 80 64 128 64 64 0
0
qdr_query_t 336 16 32 16 16 0
0
qdr_terminus_t 64 64 128 64 64 0
0
qdtm_router_t 16 64 128 64 64 0
0
> 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: 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-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
