Vector35 / Vector35/binaryninja-api
Cannot Close A Project
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: 5.1.7468-dev
- Edition: Ultimate
- OS: macOS
- OS Version: 15.5
- CPU Architecture: x64
Bug Description:
Once one project is open, it cannot be closed. Only a different project can be opened. This affects how new files are opened. If a project is open, new files will be opened in a separate instance of binja. This happens even if you X out of the project's tab. You can see that a project is still open in the lower left corner of the window.
Steps To Reproduce:
- Open a project.
- Hit the X to close the project via the tab
- Notice in the lower left corner, the project name is still shown.
- Use the Open, Open with options, or Triage buttons to open a new file.
- Notice that a whole new instance of binja has been created.
- Notice that the instance of binja with the project open is still there in the background with nothing in it and no tabs open.
Expected Behavior:
There should be a way to close a project (or when X'ing out of the project tab the project should close). Once the project is closed, new files open in the same context as the open window.
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
Reproduce the workflow on macOS: open a project, close its tab with X, then use Open, Open with, or Triage. Trace the project and tab-close handling to determine why the project remains shown in the lower-left corner and a new instance opens. Done means closing the project clears the project context and new files open in the same window.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100