Having a type selected in the types view whilst many types are being defined causes the UI to freeze

Ouverte
#8,192 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Calme
Stack technique
cpp
Domaine
desktop-dev, reverse-engineering

Piste de recherche

Start at the Types view with a type definition selected, then reproduce the freeze while analysis or a plugin creates many types, such as when loading an additional DYLD Shared Cache image. Trace the repeated updates and verify that the UI remains responsive while type creation continues and the selected definition still updates correctly.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Version and Platform (required):

  • Binary Ninja Version: 5.3.9429-dev Ultimate (ea9c02c3)
  • Edition: Ultimate
  • OS: macOS
  • OS Version: 26.4
  • CPU Architecture: M1

Bug Description:
If you have a type selected in the types view such that you can see its type definition, and a bunch of types are being created (for instance because a plugin is doing analysis that causes types to be generated automatically) the UI will freeze because it seems to be running an update on the main thread every time a new type gets created.

Even though I recognise this issue it still bites me quite often. I'll be looking at DYLD Shared Cache and at some point decide to load an additional image, forgetting about this issue and the fact I have a type selected in the types view. Then I get hit with a constant freeze until Binary Ninja can catch up which can be a long time (10s of minutes) depending on the image loaded and the number of types being created.

Additional Information:
I thought maybe I'd reported this issue before but I couldn't find it. My other issues related to the types view and UI freezing appear to have different causes.

Langage dominant
C++
Étoiles
1.3k
Forks
298
Merge moyen
5 j 5 h
PR mergées (30 j)
19

Guide de contribution

Aucun guide de contribution indexé pour ce dépôt

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de Vector35/binaryninja-api

Toutes les issues de Vector35/binaryninja-api

Issues similaires

Plus d'issues C++

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.