Skip to content
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

[Bug]Main Window Marked as Unresponsive when Dialog is open #379

Open
420noscope-exe opened this issue Jul 19, 2024 · 1 comment
Open

[Bug]Main Window Marked as Unresponsive when Dialog is open #379

420noscope-exe opened this issue Jul 19, 2024 · 1 comment

Comments

@420noscope-exe
Copy link

420noscope-exe commented Jul 19, 2024

lsb_release -a                                                  
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	24.0.4
Codename:	Wynsdey

uname -r                                                        
6.6.40-1-MANJARO

You may see me use dialogue/dialog interchangably, dialog is shorthand.

Using action ci #405 AppImage.

Expected Behavior:
The main window should ignore all user inputs while file dialogs are open, but should still be "responsive" and not halt the program. This would prevent accidental changes while the dialog is open, but would ensure that the program behaves.

Observed Behavior:
When opening a file dialog, the main window is marked "unresponsive" by the OS. Attempting to move or resize the main window with a dialog open results in graphical artifacts. CPU usage of the "AppRun" process drops to 0% when a dialog is open. This has been present since atleast release 0.13.0, and has persisted through the custom file dialogs, tinyfiledialogs, and nativefiledialogs/sbus versions/releases.

Workaround: Click "wait" or dismiss the message after the dialogue is closed. Save frequently between imports. Do not click Force Quit until you have saved.

Program becoming Unresponsive with open dialog:
Screenshot from 2024-07-19 17-31-10

Normal CPU utilization with no dialog open:
Screenshot from 2024-07-19 17-37-21

0% CPU utilization with open dialog:
Screenshot from 2024-07-19 17-37-53

@guillaumechereau
Copy link
Owner

Yes that's an issue. At least I think this should only affect the AppImage version now, since the build on linux uses gtk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants