Author Topic: FileOpenDialog crashes/freezes  (Read 480 times)


  • New Member
  • *
  • Posts: 17
FileOpenDialog crashes/freezes
« on: January 20, 2023, 08:48:30 pm »
I've just updated to Lazarus 2.2.4 with FPC 3.2.2 and now when any of my projects/applications opens a FileOpenDialog, usually via the standard FileOpenAct, the app freezes and cannot be stopped with Ctrl+F2, in fact the only way to get out of the situation is to kill the Lazarus process.

I've posted this in the Debugger section because if I run without debugging, or directly from the generated .exe, it works fine. I've tried all three debugging settings and the same thing occurs.

All I've been able to find so far was an old suggestion, from 2015, that the setting "DisableLoadSymbolsForLibraries" set true would be a solution - but we no longer have that setting.

I'm on Windows 10 - 21H2 64bit

I've changed to using GDB instead of FpDebug and now I don't suffer the freeze

I also found that "Reset debugger" from the Run menu was able to kill the frozen debugger.

« Last Edit: January 20, 2023, 10:11:27 pm by Blue_Painted »


  • Full Member
  • ***
  • Posts: 177
Re: FileOpenDialog crashes/freezes
« Reply #1 on: March 21, 2023, 02:35:30 pm »
I can confirm that this error persists in lazarus 2.2.6 with topendialog and with topenpicture dialog too.

start new project
drop a button
on button the code
Code: Pascal  [Select][+][-]
  1.  if OpenDialog1.Execute then
  2.     label1.Caption:=OpenDialog1.FileName;          

and F9... it compiles file, run ok but when click on buton application hangs. No need for breakpoint.
Tested (so far) on lazarus 2.2.6 win64 2023-03-04 fpc 3.2.2 rev 2_2_6

It hangs with fpdebug, had to select reset debugger on menu and most of the time ends well, but sometimes lazarus ide hangs and had to kill it on task manager.
I can confirm too that if i run without debugger or using gdb it works well (very very slow when opening dialog on gdb).


TinyPortal © 2005-2018