Recent

Author Topic: Error after Close; in Debug mode  (Read 460 times)

djongepier

  • New Member
  • *
  • Posts: 12
Error after Close; in Debug mode
« on: May 09, 2025, 09:39:45 am »
Hi All,

See attached screenshot.

I have started to build something small, and I always begin with low hanging fruit, I want an exit button.
Created the button, tested it to work OK. Then moved on to fill some small gaps, created the Debug and Release build configs.
After making a new debug build config with the button for it in the interface, I get the error in the picture.

Any clues on how that might have come to be?

- Windows 11 Pro
- Lazarus 3.6
- Installed via fpcupdeluxe

Martin_fr

  • Administrator
  • Hero Member
  • *
  • Posts: 12345
  • Debugger - SynEdit - and more
    • wiki
Re: Error after Close; in Debug mode
« Reply #1 on: May 09, 2025, 09:44:37 am »
This is "Heaptrc" -gh
for Project Options > Debugging

And in this case (despite the title) it says it is all OK :"0 unfreed blocks" means no memory was leaked.

djongepier

  • New Member
  • *
  • Posts: 12
Re: Error after Close; in Debug mode
« Reply #2 on: May 09, 2025, 09:47:33 am »
Hey thanks, good information then.

Last few attempts at using Lazarus, at least one time managed to lockup Windows due to not freeing memory.

Thank you for clearing this one up.

Thaddy

  • Hero Member
  • *****
  • Posts: 19163
  • Glad to be alive.
Re: Error after Close; in Debug mode
« Reply #3 on: May 09, 2025, 10:58:51 am »
I would use -gh -gl or -glh, because including the lineinfo saves time during debugging.
objects are fine constructs. You can even initialize them with constructors.

 

TinyPortal © 2005-2018