Forms internal data problem? Crashes on save form (and run)

Question

Two problems in the same form:
First, if I run the form from Developer without compiling it before (just after open), the form crashes silently, even in debugging mode.
The forms crashes in first block, after firing block level triggers and post query trigger (the data is fetched from database), but before displaying data.
This data block is on a separate window.
If I compile the form before run, it is working well. (When I run the form with Forms Runtime, it works, too.)
Now is the big trouble:
When I try to save the same form AFTER executing it from Developer, the following windows error is generated:
The instruction at "0x67fae824" referenced memory at "0x00000005". The memory could not be "read".
The form can be saved only if is not executed before from developer.
The problem persists even after reinstallation.
I suspect some form internal conditions mismatches generated by my form.
I am using Forms 6i (patch 11) on Windows 2000.
GB

Answer 1

The size looks well: 900K for FMB and 220K for FMX.
Conversion to FMT and back does not resolv the problem, I checked it before my first message.
But:
1. Form Builder crashes on save when it is executing
"rep movsd" assembler code in "CA60.calpconcat",
called by "CA60.calpcpy", called by "ifdig60. ...", etc...
2. When converting back FMT to FMX, the builder expands dramatically it's internal memory to about 1.2 GB (!).
It can be a buffer overflow generated by some conditions in my form?
GB