I don't think that the PC is the problem ... it's a Lenovo ThinkPad T520 with an Intel Core i7, 16 GB memory and is running on Windows 7.

As far as I remember you once mentioned that in debug mode internal xml data is built up ... can it be that there's a problem?

Is there a way to check for broken files by tool? Our project consists of such a high number of files that it might get hard to find a broken one.
Is it for example possible to write some more information into the logfile while SED (or the engine when started with -debug) is compiling data / loading files? So that would be an indicator to the broken file.

I normally never use the Debug Run but sometimes I click on it by accident. Every time I get the same Runtime Error, and when I close the dialog box I get a Windows "Script Editor has stopped working" message which forces me to close SED.
I'm starting to believe more and more that this is (only) related to the size of the program, not to its actual files itself (and thus probably a SED bug).

In our project all files are organized by type in different folders (e.g. pics, models, rooms ...).

I just removed all PRAGMA_PATH and PRAGMA_LEVEL entries from the main file to avoid loading any files but just .c and .h.

In debug mode SED is still crashing.

Can you confirm that when you start it out of an empty folder with no files except for the script, it still crashes? Can you then upload that script? I can look into it, maybe I see the reason of the problem.

Yes, I can confirm the crash.

I copied all .c and .h files into a new folder and removed all PRAGMA_PATH and PRAGMA_LEVEL entries. SED still crashes in debug mode while compiling.

I just sent this version by mail and hope that this helps to find where the problem comes from.

Anbei die Antwort vom Support:

-------------------------

Hallo Herr Galla,

wir konnten das Problem zuerst nicht reproduzieren, haben jetzt aber die vermutliche Ursache gefunden - der Code mit Debugdaten belegt schlicht zu viel Speicher. Wenn der virtuelle Speicher verbraucht ist, stürzt der Compiler ab, da hier - im Gegensatz zur Engine - eine fehlgeschlagene Speicherallokation nicht abgefangen wird.

Da sich der benötigte Speicher auf die Schnelle nicht reduzieren lässt, wäre die Lösung zum Debuggen, dass Sie Ihren Code in verschiedene Module aufteilen und diese einzeln debuggen.

Mit freundlichen Grüßen
Support / Gamestudio

-------------------------