MacOS creates new windows from CLI

Open
#8,501 0 comments 0 reactions 0 assignees View on GitHub

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
Active
Tech stack
cpp, macos
Domain
cli, desktop

Research direction

Start by reproducing the listed project-opening and binaryninja URL commands on macOS, including repeated opens, and compare the window and tab behavior with Windows or Linux. Trace the CLI and URL-handling entry points involved in those actions. Done means opening an existing or new project navigates predictably without unwanted windows, tabs, or reloads.

Written by the indexing model from the issue text.

Description

Version and Platform (required):

  • Binary Ninja Version: 6.0.1561
  • Edition: Ultimate
  • OS: MacOS
  • OS Version: 26 and 27
  • CPU Architecture: M3 Pro

Bug Description:
MacOS windows and tabs are not functioning correctly. Here is a couple of examples of behavior:

  1. Opening a project that hasn't been opened this session will cause the window to rapidly close and reopen to the project browser.

  2. Opening a project that has been opened this session will leave the first new tab openImage

  3. Opening a Binary Ninja URL from command line with open binaryninja:/.... will always make a new window, which does not happen on Windows or Linux.

  4. Open binaryninja:/bin/ls?expr=0x404da0+0n8 twice and observe that it makes a new tab of the same binary rather than navigating to a new one.

Image

Additional Information:
I think these are all connected bugs which is why I'm filing them together. If necessary we can break this up into sub-issues. I don't think it is a Qt problem, due to the CLI not working either.

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Vector35/binaryninja-api

All issues in Vector35/binaryninja-api

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.