Hi support,

when I try to run my project from SED in debug mode I get a runtime error:

-----------------------------------------------------------
Runtime Error!

Program: D:\Apps\GStudio8\SED.exe

This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

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

Any hints what the problem might be?

Regards,
Sascha.

This sounds like a crash in the game - a random crash that only happens in debug mode. It is no direct crash in the script, otherwise you'd see an error message, but something else, like a subsequent crash due to a script problem, or a damaged file.

I would remove parts of the project until it does not crash anymore, then move them back step by step. This is the best method for finding random crashes.

I get that crash while the engine is compiling the code ... somewhere at about 50%. Is there any memory limit for debug mode? The project is quite big.

There is a limit, but you should get an error message when it is reached. But when using object definitions in the code, such as images or sounds, the files are loading at compile time - so that also points towards a damaged file. You could temporarily replace all files by dummys and check if this solves the problem.

Currently I'm running through subversion revisions to find the point where we got this issue.

I already found a rev that doesn't crash and started doing a binary search. So I should find the file that causes the issue soon.

@JCL if this is really related to a defect file which is loaded, maybe adding an Exceptionhandler around loading/processing files might be possible? In this case it might be possible to printout the filename when it occurs to avoid searching.

There are lots of exception handlers in Gamestudio, but as you can see here, even they can not catch anything.

I know this is nitpicking but the word choice certainly amuses me. :3

Unfortunately the problem isn't that easy to fix than I thought.

Either I get a "e1005 out of memory" error but no SED crash (something we discussed somewhere in 2011 before ... while compiling SED consumes more than 1GB of memory in debug mode) or I just crashes in debug mode when using the current revision.

Currently I'm not sure if it's really a broken file.

E1005 can not be caused by just consuming 1 GB memory, unless your PC is very old or you have strange settings in the Windows memory management. A modern PC has enough virtual memory.

All this are strong indicators of a broken file.