UI interactions are queued when app lags, which leads to unpredictable behaviour

Since Source tree has been re-written from the old skeuomorphism to a new flat design its performance became terrible, and still, in 2023 it often lags and freezes a lot even on the  latest Mac m1 CPUs, which indicates a very bad coding, QA, management etc skills of the team.

But moreover, when app freezes and you try to click some elements on the screen, for example:

1) you clicked right mouse button on some unstaged file

2) then app freezes because of crappy app code

3) and you click left button on the next unstaged file

4) then the app unfreezes context menu is opened from the first right click

5) but left click happens not on the element you clicked, but  in the context menu which you haven't even seen while clicking LMB

6) something unpredictable happens depending on your luck (Remove? Stop tracking? anything else).

How should be:

App never blocks the UI thread for longer than 16ms on lower end devices.

• But if it is too hard to implement by your team, and I would say it is probably impossible due to their incompetence, lets just not enqueue UI interactions for too long.