Bug 32949 - Huge memory consumption of libabigail on big ELF/DWARF binaries
Summary: Huge memory consumption of libabigail on big ELF/DWARF binaries
Status: NEW
Alias: None
Product: libabigail
Classification: Unclassified
Component: default (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-05-09 14:45 UTC by Dodji Seketeli
Modified: 2025-05-22 10:29 UTC (History)
4 users (show)

See Also:
Host:
Target:
Build:
Last reconfirmed:
Project(s) to access:
ssh public key:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dodji Seketeli 2025-05-09 14:45:22 UTC 
When using abidiff to compare binaries of Fedora package rocm-compilersupport-19-3.rocm6.4.0.fc43 against rocm-compilersupport-19-6.rocm6.4.0.fc43, memory consumption can shoot up to more than 22GB of RAM.

It would be important to analyze why and where the memory is being used so much and try to bring it down.
Comment 1 Miroslav Vadkerti 2025-05-12 07:25:07 UTC 
We see similar issue with webkit2gtk3:

```
abidiff --d1 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/before/aarch64/usr/lib/debug/ --hd1 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/before/aarch64/usr/include --d2 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/after/aarch64/usr/lib/debug/ --hd2 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/after/aarch64/usr/include /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/before/aarch64/usr/lib64/libjavascriptcoregtk-4.0.so.18.25.15 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/after/aarch64/usr/lib64/libjavascriptcoregtk-4.0.so.18.27.4
```

Do we need another issue for this one?
Comment 2 Miroslav Vadkerti 2025-05-12 07:25:07 UTC 
We see similar issue with webkit2gtk3:

```
abidiff --d1 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/before/aarch64/usr/lib/debug/ --hd1 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/before/aarch64/usr/include --d2 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/after/aarch64/usr/lib/debug/ --hd2 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/after/aarch64/usr/include /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/before/aarch64/usr/lib64/libjavascriptcoregtk-4.0.so.18.25.15 /var/ARTIFACTS/work-rpminspectd2rzb0yz/rpminspect/tree/workdir/webkit2gtk3-2.48.1.qloJVn/root/after/aarch64/usr/lib64/libjavascriptcoregtk-4.0.so.18.27.4
```

Do we need another issue for this one?
Comment 3 Mark Wielaard 2025-05-22 10:29:22 UTC 
Seen the same for valgrind on a c9s build. Apparently centos builds cannot use more than 8GB of memory for rpminspect checks. So even relatively small packages/binaries like valgrind get caught by this. Dunno if a limit of 8GB is reasonable for running libabigail in general?