Message Areas - "Route Editor 'memory leak'"

Train-Sim.Com Message Areas

"Route Editor 'memory leak'"

Email this topic to a friend
Printer-friendly version of this topic
Bookmark this topic (Registered users only)
Previous Topic | Next Topic Conferences MSTS Route Design (Protected) Original message
rdamurphy (167 posts)
Dec-01-01, 05:29 PM (EST) "Route Editor 'memory leak'" Just to clarify, since I've seen it so often, the Route Editor does not have a memeory "leak". A memory leak occurs when an application allocates memory to create an object, then fails to release that memory (garbage collection) when the application exits or when the object is destroyed. What occurs with the Route Editor is that when you enter it, it draws the tile you are in, plus any you can see. When you move along the route, it draws another tile, and retains in memory the tiles behind you. This is why 'flying' through the route to get to the part you are working on is a bad idea. "Jump" to it with the camera instead or change your start tile. By the way, a memory leak is a mistake, the Route Editor's behaviour is by design.Still working on the Railroad.Rob Alert Edit | Reply | Reply With Quote | Top
Table of Contents

Subject Author Message Date ID RE: Route Editor 'memory leak' bobs Dec-01-01 1 RE: Route Editor 'memory leak' jeffmorris Dec-01-01 2 RE: Route Editor 'memory leak' rdamurphy Dec-01-01 3 RE: Route Editor 'memory leak' derekmorton Dec-02-01 4 RE: Route Editor 'memory leak' bobs Dec-02-01 5 RE: Route Editor 'memory leak' rdamurphy Dec-03-01 6

Lobby | Topics | Previous Topic | Next Topic
Messages in this topic
bobs (241 posts)
Dec-01-01, 05:53 PM (EST) 1. "RE: Route Editor 'memory leak'" I think not.If what you said was true, then shutting down the Route Editor should put your system back to normal. Doesn't happen. Without a reboot I don't get my memory back. I can't restart the route editor, and several other programs will not start either, ones that aren't part of MSTS.As you fly over the route, you will see pauses as the code loads new objects that are coming into view. Stop and turn around and go the other way. If what you said was true, you would be able to fly back the way you came without ever seeing the pauses. That doesn't happen either. The editor pauses and loads the objects, no matter which way you go. Remove | Alert Edit | Reply | Reply With Quote | Top
jeffmorris (366 posts)
Dec-01-01, 06:11 PM (EST) 2. "RE: Route Editor 'memory leak'" Not True. Route Editor "leaks" memory in Windows 95/98/ME. It doesn't "leak" memory in Windows 2000/XP. When I ran Route Editor on my computer running Windows ME, I had to save my route, exit Route Editor, reboot my computer, run Route Editor, load my route into Route Editor, and work on my route for five to 20 minutes before I have to repeat these steps. When I run Route Editor on my computer running Windows XP, I was able to work on my route for several hours without having to go through these steps. Jeffrey. Remove | Alert Edit | Reply | Reply With Quote | Top
rdamurphy (167 posts)
Dec-01-01, 06:26 PM (EST) 3. "RE: Route Editor 'memory leak'" Which probably points to a problem with Win 9x (to which I'll refrain from mentioning is now obsolete) and DirectX, rather than with the Editor. I have also noticed problems with apps programmed on NT based systems running on 9x systems, though there shouldn't be any difference in the executables. One of the weaknesses of 9x is in inability to "reclaim" memory released by an application. Also note that if an application exits abnormally, such as a crash to desktop, any garbage collection or clean-up code will not execute, and the memory will not be released. As for the halts while travelling through the route, this could also occur if Windows is writing Ram to Virtual Memory, and must recover the information from the Hard-drive cache. It could also occur if the video system is incapable of re-drawing the screen at the speed you are traveling through the scene. Try supersonic flying in Flight-Sim at low altitude...Rob Remove | Alert Edit | Reply | Reply With Quote | Top
derekmorton (222 posts)
Dec-02-01, 02:31 AM (EST) 4. "RE: Route Editor 'memory leak'" >Which probably points to a problem with Win 9x (to which
>I'll refrain from mentioning is now obsolete)Thats only windows 95> and DirectX, rather than with the Editor.The problem is within the editor

>I have also noticed problems with apps programmed on NT
>based systems running on 9x systems,Is this relavent to the discussion about the route editor?>though there shouldn't be any difference in the executables.and there isn't.

>One of the weaknesses of 9x is in inability
>to "reclaim" memory released by an application.Neither win9x or NT/2k/xp 'reclaim' memory, it is up to the application to 'release' memory.>Also note that if an application
>exits abnormally, such as a
>crash to desktop, any garbage
>collection or clean-up code will
>not execute, and the memory
>will not be released.Very trueDerek EngMod@leder.com.au
Remove | Alert Edit | Reply | Reply With Quote | Top
bobs (241 posts)
Dec-02-01, 08:12 PM (EST) 5. "RE: Route Editor 'memory leak'" I don't much care where the problem is. It is Microsoft's operating system and their simulator, no matter who wrote it. That makes it their problem. Remove | Alert Edit | Reply | Reply With Quote | Top
rdamurphy (167 posts)
Dec-03-01, 00:14 AM (EST) 6. "RE: Route Editor 'memory leak'" Hmmm, Good point.Rob Remove | Alert Edit | Reply | Reply With Quote | Top

Lock | Archive | Remove

Lobby | Topics | Previous Topic | Next Topic