Vector35 / Vector35/binaryninja-api
macOS inconsistent startup with regards to existing windows compared to Windows/Linux
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
Due to issues with the method used to track shared instances, macOS currently does NOT try to open an existing instance of BN if one is already running but when launched from the CLI will always launch a new instance. This is inconsistent with Windows and Linux where we default to re-using existing processes.
https://github.com/Vector35/binaryninja/commit/0c82c95b95dd22b8faf46ee4831b8789b349d815 is the internal commit for anyone following up on this later.
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 reviewing the referenced internal commit and comparing macOS startup and shared-instance handling with the existing Windows and Linux behavior. Done means launching Binary Ninja from the macOS CLI reuses an existing instance when one is already running, rather than always opening a new instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, macos
- Domain
- cli, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100