Feature map uses a significant amount of memory after loading a shared cache
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- desktop-dev, reverse-engineering
Research direction
Reproduce the issue by opening the specified dyld shared cache and loading CoreFoundation, Foundation, AppKit, and CFNetwork. Profile the feature map's memory after those images load and inspect how the rendered mapped regions are retained. Done means the feature map uses substantially less memory while still displaying the mapped regions correctly.
Written by the indexing model from the issue text.
Description
Version and Platform (required):
- Binary Ninja Version: 5.2.8071-dev Ultimate, bab15a22
- OS: macos
- OS Version: 15.5
- CPU Architecture: arm64
Bug Description:
After opening a macOS shared cache and loading a couple of images, the feature map ends up with around 100MB of data allocated that represents the rendered version of the mapped memory regions. That feels excessive given that it is by default displayed in a view roughly 64 x [display height] pixels tall. On my Mac that's roughly 64 x ~1350, which should be representable in less than 100KB of memory.
Steps To Reproduce:
- Open /System/Cryptexes/OS/System/Library/dyld/dyld_shared_cache_arm64e
- Load a CoreFoundation, Foundation, AppKit, and CFNetwork.
- Check the memory usage of the feature map
Expected Behavior:
Less.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Vector35/binaryninja-api
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8540 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Vector35/binaryninja-api#8516 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Vector35/binaryninja-api#8503 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8446 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Vector35/binaryninja-api#8444 ·
All issues in Vector35/binaryninja-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·