Vector35 / Vector35/binaryninja-api
potential performance regression when testing chrome.dll
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Version and Platform (required):
- Binary Ninja Version: 3.6.4671-dev
- OS: Believe it's OS independent, haven't tested for sure given the long turn-around time
- CPU Architecture: Both according to user reports
Bug Description:
Testing a recent chrome.dll reveals that after some time, analysis is only using 1-2 cores. This appears to be a regression or maybe a specific bug with this file.
Steps To Reproduce:
Please provide all steps required to reproduce the behavior:
- Search internal slack for "clip apples leap mammoth"
- Open the file, disable linear sweep and function pointer weep
Expected Behavior:
Analysis finishes in less than 15hrs...
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.
Research direction
Start by reproducing the report with the specified chrome.dll, using the Binary Ninja version listed and disabling linear sweep and function pointer sweep. Compare analysis duration and core utilization against the expected completion time of under 15 hours; the issue names no source file or test to inspect.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- reverse-engineering
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100