[Bug binutils/29785] New: memory bloat in version 2.39

[lijunlong at openresty dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=29785

            Bug ID: 29785
           Summary: memory bloat in version 2.39
           Product: binutils
           Version: 2.39
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: binutils
          Assignee: unassigned at sourceware dot org
          Reporter: lijunlong at openresty dot com
  Target Milestone: ---

I think maybe the commit b43771b045fb5616da396 introduces this problem.
In version 2.37, addr2line uses less memory and runs faster.

I run the following cmd

time /usr/local/bin/addr2line -a -f -i -e mysqld.debug a77563 b3cabf 4f7eaa
9be700 a3dee8 b05b87 afecba aa8cd2 51f53e 52d0e4 9c0da9 9bad63 9bfb0a 9c0c26
a3b8e0 a3a7bf a3c0d9 99fe9f 9c1253 52bc4f


the version 2.37 runs for 8s while the version 2.39 runs for 1m58s.
and the version 2.37 use about 8G memory while the version 2.39 use 16.8G
memory.


the hot backtrace of the version 2.39 from flamegraph is:


_start
__libc_start_main
main@binutils/addr2line.c:579
process_file@binutils/addr2line.c:470
translate_addresses@binutils/addr2line.c:337
bfd_map_over_sections@bfd/section.c:1369
find_address_in_section@binutils/addr2line.c:177
find_address_in_section@binutils/addr2line.c:197
_bfd_elf_find_nearest_line@bfd/elf.c:9309
_bfd_dwarf2_find_nearest_line@./dwarf2.c:5854
comp_unit_find_nearest_line@./dwarf2.c:4598
comp_unit_maybe_decode_line_info@./dwarf2.c:4631
decode_line_info@./dwarf2.c:2863
arange_add@./dwarf2.c:2213
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2191
insert_arange_in_trie@./dwarf2.c:2076

-- 
You are receiving this mail because:
You are on the CC list for the bug.