x86_64-win64 annoys me lazarus / 21-General ---------------------------------------------------------------------- Nicole · 2025-06-17 18:28 My project contains a lot of frames, all built the same. The compiler keeps cheating, "this one is missing". And names one, which looks alike all others, every time the same. I checked it all: Frame, path, lpi,... nothing to find. When I delete the x86_64-win64 directory, then it works again. For one single run. How to deal with it? ---------------------------------------------------------------------- Joanna · 2025-07-14 13:48 I create frames at runtime. It prevents them from doing strange things. ---------------------------------------------------------------------- Martin_fr · 2025-07-14 13:56 Quote from: Nicole on June 17, 2025, 08:28:16 pmThe compiler keeps cheating, "this one is missing". This is an error you get - during compilation? - at runtime (when the app starts up)? Does the error happen when - you make/made changes to the frame - make changes to the form that contains the frame   (or a frame containing another frame / and the error is for the "another frame") Are all the "frames" (the pascal files for them) part of the project? Are they listed in the "project inspector"? (Or if they are in packages, ore the in their packages file lists) ---------------------------------------------------------------------- H₂SO₄ · 2025-07-14 13:58 Your project must have a weird structure. Can you post the output of  tree /f  in the project's root directory together with your  .lpi? ---------------------------------------------------------------------- paule32 · 2025-07-14 15:32 I bet it is a recursive stack problem. calling the Frame form Frame again and again ... like if you look into a 3 Panel'ed flexible Mirror and you move the two outer Mirrors in various Degrees - then you have a Loopback. and when the Stack is full - boom crash .... ---------------------------------------------------------------------- Nicole · 2025-07-14 15:41 In the meanwhile I have forgotten about this thread. The problem ended as it came and I do not know, what was the reason.