Hey

Many times it has been reported, that if you program a lot with 3D Gamestudio, 3DGS leaves always some memory leaks (~200 KB - 3MB) in your memory (has always beend dispatched by jcl) which is leading to an ERROR E1241: D3D device open failure / ERROR E1242: Video device open failure" (or you get other graphical errors, like wrong resolution or white skins/panels etc.)

I spent a bit more time into this error and now i found out that this error always appears after a long time of programing with sed.
Example: I start the engine 100 times and everything is working fine (i haven't done this because of this test but because I'm a perfectionst -> 1000ends of restarts ). After a reboot and serveral engine starts I write a big bunch of code (around 500 Lines) in ~1 hour - doing nothing more than programming - -> The engine crashs with the Error mentioned above.

This was not the only time... I always have the opinion, that after a long time of programming with BIG scripts (~10.000 lines) the engine crashs not because of memory leaks of the engine, but because of an fault in SED.

Why am I posting this here? Before I want to write this in a Bug Report, I want to hear your opionon.. Is it actually possible to get such a crash because of SED? Anyone made the same expericences?

Thanks
TripleX

i mentioned this , too some time ago. its definately sed that causes everything crashing. i first thought it was wed or the engine, but i found out its sed, too.

i have the problem, that whenever i have sed and wed open the same time after i switch to wed with alt-tab wed just crashes.

this only happens when sed is open. wed alone is running fine, sed alone also makes no problems for me.

but if i run both at the same time, i only have to switch a couple of times using alt tab and then wed crashes.

i agree with everything TripleX said... since it happened here already a couple times as well

Does this only happen, if you start the engine from SED? If you do, you can try to start the engine with a bat file:
Code:

---

C:\Proramme\GStudio6\bin starter.wdl -nx 500

---

I do this like I said, and there happens never something.

I've never had this problem actually. I always use SED for my programming and spend everyday coding. Alt+ tab to switch between "sed and wed" and "Wed and sed" gives me no problems.

The biggest problem I've had here is that SED uses way to much memory to just be a fancy notepad.

I'm not saying anyone is wrong, just that I have no had this problem.

I had this experience too, as the others here.
And this is not only since the last Betas, it happened also since the 6.3x versions:
http://www.coniserver.net/ubbthreads/sho...;page=10#441564

And i'm also used SED every time, maybe I should try it with MS VisualStudio instead (if i have too much time like TripleX ).
old_bill

There is a major bug in SED that, as you type in SED, the system's resources gradually decrease. In my 2D game, for example, which is nothing more than panels and a 10,000-line script, when I'm typing up a long script, I watch my resources go from 52% free to just 14% free in about an hour. The fix (temporary) is to close SED, wait a few seconds for the resources to replenish and reopen SED.

A quick way to get SED to crash from this is to run the engine through SED, press control+escape to return to windows then use control+alt+delete and end the task of the engine. Then, in SED, type even one character and wait. The resources drop 9% in just 2 minutes and they will continue to drop as long as SED is the active window. I reported this crash bug quite a while ago. In my case, I was using a breakpoint_on instruction (for debugging) and when I pressed Esc to exit the engine, it didn't work, even after several tries. I had to resort to closing the engine in a remote way (control+escape to get into windows to do that, learned this accidentally two years ago) since there was no other way to close the engine (I was running in full screen so I couldn't click the X in the corner or right-click on the window in the task bar to close it that way).

call me silly, but couldn't you just use your mouse to open wed? If it's already open, it's just a tasbar button away :P Thats how I switch between programs, and I never had a problem, of course, i dont write lotsa scripts either...

Jason