We had previous reports on this. And according to them it works well with Lazarus 2.3. (which means ok for the next release 2.4).
If you need to debug such an app, you can switch to the GDB debugger. And also (with gdb) maybe set "DisableLoadSymbolsForLibraries" (global options for gdb debugger).
I have never been able to reproduce it. So I can't tell why this may happen or what may have fixed it.
(On Windows) The issues with any open/save/... dialog is that they load lots of 3rd party libraries (shell extensions). Those libraries may react to being debugged. Or they may contain code that triggered a (meanwhile fixed) bug in the debugger.
Of course it can also be interaction with Microsoft defender, or any other anti virus. And here again, it can be a combination of settings/software specific to a few systems.
Last not least (though likely not the issue here). Fpc 3.2.2 has a bug in the optimizer. If you compile your IDE (Lazaurs itself / not your project) with -O2 (or higher) then the IDE will crash. Actually it is the debugger in the IDE that may crash. And such a crash may not identify as crash, but could lead to the debugger hanging.