ansaurus

Question

Why "menus" unit is finalized too early?

Answer 1

+2 A:

Make sure that FastMM4 is the FIRST line in your project file's uses clause (project|View source). If its not there, then add it.

skamradt 2010-03-26 17:33:24

Answer 2

+2 A:

It looks like one of your forms is getting destroyed after Menus.pas has been finalized. If your form has a menu on it, it would probably have to have Menus in its uses list in the interface section, which should make this impossible.

The only time I've seen issues like this pop up (no pun intended) is when using packages. Are you perhaps using a DPK with a plugin that adds a popup menu or menu items to your program? Package finalization can do some strange things to your program if you're not careful.

Either way, the solution is probably to dispose of the menu yourself before menus.pas finalizes. When it's time for the program to shut down, call Free on your popup menu and see if that solves the problem.

Mason Wheeler 2010-03-26 17:51:12

Yes, that was the point of the question, why menus.pas is finalized too early, before all forms have been finalized.I'm not sure about the packages, I think there should be none of that kind, but I'll have to check.

Harriv 2010-03-26 20:38:55

Answer 3

+3 A:

I've seen such problems with Delphi 2007 before. Sometimes the compiler gets confused and generates incorrect initialization or finalization order. Sadly, I was never able to create a reproducible test case to send to the CodeGear/Embarcadero people.

Whenever that happened, a full rebuild helped.

gabr 2010-03-26 19:39:26

Answer 4

+4 A:

That situation can happens when a unit finalize after another unit it indirectly depends on.

For exemple, take the following unit:

unit Unit1;
interface
uses
  Contnrs;

var
  ItemHolder : TObjectList;

implementation

initialization
  ItemHolder := TObjectList.Create(True);
finalization
  ItemHolder.Free;
end.

That unit only directly depends on Contnrs. For that reason, delphi will ensure that this unit is finalized before Contnrs is. If the ObjectList contains TForms, Delphi won't ensure that Unit1 is finalized before unit Forms. If there are still some forms left while closing the application, TObjectList (Since it owns the object) will free the items it contains(Call TForm.Free). But since Unit1 doesn't depends on TForm, it's possible that the unit Forms is already finalized and that TForm.Destroy isn't in memory anymore.

This is why you need to be very carefull about what you do in finalization sections.

I'm not sure it's the source of your problem, but I would look that way first.

Ken Bourassa 2010-03-26 20:05:35

ansaurus

tags:

views:

answers:

Why "menus" unit is finalized too early?

related questions