Never had any of these issues on Linux. Geany would load the full session in <1s, never frozen.
No plugins.

Behavior:

1. Geany takes about 20 seconds to startup/load.
   Only about 20 documents open with about 10-15k lines of code total.
   Memory usage after done loading/starting up: 16MB.
2. This happens about 80% of the time. Sometimes Geany opens normally.
   Sidebar, tabs and editing window is frozen (can't type, can't highlight text, can't resize the boundary between sidebar and editing window, etc.
   Only the menu and toolbar seem responsive.
   Also, if opening a second geany window, the second window is responsive (no session).
   If I re-open a session in the second window, it takes about 20 seconds again to load (up to several seconds for a single file), however the interface is responsive.

Here's how the app looks (all text and filenames removed): https://i.imgur.com/GnZEnWN.png
The sidebar is really small and can't be resized while frozen. Everything else looks visually normally.

The most consistent way I've found to get Geany unfrozen is by clicking a different tab than the one already open towards the center left side of the screen, though this will often close a tab even though you're not touching a X (upon unfreezing, the tabs shifts somewards towards the right, the sidebar resizes to the previously used size, etc).
Randomly clicking spots in the text will sometimes work too, but it's inconsistent.

Update: looks like a factor to whether Geany will be frozen after loading up or not depends on the size of the currently = previously selected/focused file.
With a C++ file of 900 lines total selected Geany opened consistently in a frozen state.
With a C++ file of only 15 lines total selected Geany opened consistently in an unfrozen/responsive/proper state.
Loading times is the same in both cases though.
In sharp contrast notepad++ opens the same files in <1s after opening the application on Windows, so it's definitely not the files or the filesystem that's at fault.
Casually monitoring geany.exe: it's utilizing almost a full CPU core while loading files, but its memory is only increasing by about 0.25MB/s.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.