background/incremental saving

Open
#2,122 2 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
databases, desktop

Research direction

Start by reproducing the 45–50 second save on the described 25MB binary in Binary Ninja 2.2.2487 on macOS and identify which database updates block the UI. Then trace the save path and determine how incremental on-disk updates could preserve unsaved work without corrupting the database. Done means changes are persisted continuously or at a defined safe cadence while the UI remains usable.

Written by the indexing model from the issue text.

Description

Component: Database Effort: High Impact: High

On the binary I'm currently looking at (which is 25MB), on Binary Ninja 2.2.2487 on a MacBook Pro, pressing "save" takes around 45-50 seconds every time. That's pretty slow, and since it blocks the whole UI it naturally means I can't save very often, and have to risk losing unsaved work. It would be much nicer if Binary Ninja could continuously update the database on disk as changes are made.

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.