Using geany for many years, I found a bug on Windows 7 version. Note that I had 4 instances of Geany running when i found the bug.
To reproduce: 1. Create a folder; 2. Run Geany and click on "Open file"; 3. Go into the previously created folder using the "Open file" window; 3. Delete the folder created in step 1 4. Alert ! Geany is not responding and increase memory consumption. We can only close it by killing the process.
Desired behavior: "Open file" window should automatically detect folder deletion and show the parent tree folder.
Using Geany version 1.33
Are you using GTK+ dialogs (default) or native dialogs? (under `Edit->Preferences->General->Miscellaneous->Use Windows native dialogs`)
I am using GTK+ dialogs. The "Use Windows native dialogs" (in fr "Utiliser les boîtes de dialogue Windows") is unchecked. Should it be ?
With the native Windows dialogs you cannot delete the opened folder as the Windows dialogs lock it.
With GTK+ dialogs I cannot reproduce the described behaviour on Windows 7. Since we don't do anything special with the dialog, I guess this might be a GTK+ issue. Though it's hard to say without being able to reproduce.
Ok thanks for your responses.
Please note that on my system, the native Windows dialogs do not lock any directories. Windows dialogs that display a directory while it's being deleted detect it and display the parent directory without throwing any errors. But I guess It's probably a windows 7 settings.
Anyway, It's not a critical issue, I will pay attention to this situation in the future.
This sounds like ye olde crasher bug in GTK when the filesystem contents changes and a file chooser dialog is showing it. AFAIK, it should have been fixed a while ago in GTK, though. I'm not sure which version should have fixed it and I can't seem to find the bug reports just now, but if the GTK version we bundle on Windows suffers from the issue we might wanna try and get a newer version (yeah I know how annoying it is).
Well, on Windows we bundle always the latest available GTK version in MSYS2. Currently, this is GTK 2.24.32 with GLib 2.56.2.
I was just able to reproduce it, though it took me a couple of attempts to trigger it. Unfortunately, the gdb prompt doesn't react on Ctrl-C to interrupt the process and get a backtrace :(. Also, there were no related GTK warnings or other output on stdout/stderr.
github-comments@lists.geany.org