Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible Memory leak in OSPF: new route node #13253

Closed
ryndia opened this issue Apr 11, 2023 · 2 comments
Closed

Possible Memory leak in OSPF: new route node #13253

ryndia opened this issue Apr 11, 2023 · 2 comments
Labels
triage Needs further investigation

Comments

@ryndia
Copy link
Contributor

ryndia commented Apr 11, 2023

Hello, while investigating some stack trace for memory leak, I came across stack trace such as below repeating, I suppose this is a false positive. However, to be sure, I would like to have a confirmation if this is a false positive memory leak generated by asan.

./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017:Indirect leak of 1200 byte(s) in 10 object(s) allocated from:
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #0 0x7f052b05a037 in __interceptor_calloc ../../../../src/libsanitizer/asan/asan_malloc_linux.cpp:154
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #1 0x7f052ac5ee38 in qcalloc lib/memory.c:105
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #2 0x7f052ad11793 in route_node_create lib/table.c:481
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #3 0x7f052ad0ed5d in route_node_new lib/table.c:52
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #4 0x7f052ad0ed7b in route_node_set lib/table.c:61
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #5 0x7f052ad10ced in route_node_get lib/table.c:319
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #6 0x5583cd1dede3 in ospf_intra_add_stub ospfd/ospf_route.c:557
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #7 0x5583cd0ec42d in ospf_spf_process_stubs ospfd/ospf_spf.c:1624
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #8 0x5583cd0ec592 in ospf_spf_process_stubs ospfd/ospf_spf.c:1647
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #9 0x5583cd0ec592 in ospf_spf_process_stubs ospfd/ospf_spf.c:1647
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #10 0x5583cd0ed0f0 in ospf_spf_calculate ospfd/ospf_spf.c:1787
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #11 0x5583cd0f3ae7 in ospf_ti_lfa_generate_q_spaces ospfd/ospf_ti_lfa.c:669
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #12 0x5583cd0f48e0 in ospf_ti_lfa_generate_p_space ospfd/ospf_ti_lfa.c:807
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #13 0x5583cd0f5301 in ospf_ti_lfa_generate_p_spaces ospfd/ospf_ti_lfa.c:918
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #14 0x5583cd0f696f in ospf_ti_lfa_compute ospfd/ospf_ti_lfa.c:1095
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #15 0x5583cd0ed45e in ospf_spf_calculate_area ospfd/ospf_spf.c:1811
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #16 0x5583cd0ed77f in ospf_spf_calculate_areas ospfd/ospf_spf.c:1840
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #17 0x5583cd0ed9a3 in ospf_spf_calculate_schedule_worker ospfd/ospf_spf.c:1871
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #18 0x7f052ad2a010 in thread_call lib/thread.c:1991
./ospf_tilfa_topo1.test_ospf_tilfa_topo1/rt1.ospfd.asan.1047017-    #19 0x7f052ac22418 in frr_run lib/libfrr.c:1185
--

@ryndia ryndia added the triage Needs further investigation label Apr 11, 2023
@github-actions
Copy link

github-actions bot commented Oct 9, 2023

This issue is stale because it has been open 180 days with no activity. Comment or remove the autoclose label in order to avoid having this issue closed.

@frrbot
Copy link

frrbot bot commented Oct 9, 2023

This issue will be automatically closed in the specified period unless there is further activity.

@ryndia ryndia closed this as completed Oct 10, 2023
@frrbot frrbot bot removed the autoclose label Oct 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Needs further investigation
Projects
None yet
Development

No branches or pull requests

1 participant