-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Opening the Run Configurations Dialog Freezes UI #3
Comments
Just not to forget, see vi-eclipse/Eclipse-JDT#8 (comment) for further ideas. |
Looking back at this issue, I think we should stick to simpler solutions first like moving the long-running operations to the activation of the tabs (vi-eclipse/Eclipse-PDE#2), adding progress indicators (eclipse-jdt/eclipse.jdt.ui#675) and -if necessary- making the operation cancelable (vi-eclipse/Eclipse-PDE#3). @HeikoKlare what do you say if we keep this issue as an umbrella for all other smaller issues? If you agree to it, I can change the description of this issue and start listing the known issues and PRs related to it and we can also add new specific issues later. I also briefly tested the performance of the Launch Configurations Dialog in our PV workspace and is looking fine so I don't have any specific issues/proposals to add to this umbrella issue right now. |
Yes, this should serve as an umbrella issue. Seems like I accidentally moved it to the wrong backlog category, as it had been placed under "Aggregates" and is not part of "Ready: Atomic" instead of "Ready: Epics". |
👍
Ok. I currently have no proposals though, since the 2 "big" issues (calculation of the class hierarchies for JUnit configs and Tracing Options for the PDE configs) have been addressed and the solution is good enough. |
Options for ImprovementHere are some further options for improvement that we have discussed and that may be taken in the future for a more sustainable avoidance of freezes in the run configurations dialog. Those approaches would ensure that even in case of regressions w.r.t. single data providers for the dialog, it will still stay responsive (i.e., it will avoid performance regressions such as the (pre-)existing ones).
|
Current Behavior
Opening the "Run Configurations" dialog indeterministically takes a long time, in particular when first opened after starting Eclipse. It freezes the UI for a multitude of seconds.
EDIT: this behavior is due to several bad implementations that contribute to an overall bad performance. This issue will then serve as an umbrella for such smaller issues.
Expected Behavior
The "Run Configurations" dialog opens fast or shows some progress dialog to indicate what is taking so much time to open it. If the operation is still too slow and can NOT be optimized, the operation should be cancelable and the UI should react properly.
The specific solutions applied for each specific issue should be documented in the issue itself.
Further ideas (they should be addressed in the specific issues) can be found in this comment: vi-eclipse/Eclipse-JDT#8 (comment). Shortly summarized:
Tasks
The text was updated successfully, but these errors were encountered: