CompuServe Messages

Ethan, WP uses libraries to do it overlays. What this means is that the spell checker (for example) is not part of the main WP program, but rather that it is loaded when the user needs it. Because this code is in the form of a library (a system supported method for sharing and loading extra code) it remains in memory when WP exits. One very important feature of libraries is that they stay in memory until the OS decides the memory for something else (and no one is using the library). This has the benefit of being able to keep all the extra code in memory for later use, and IF something else needs the memory the OS can easily reclaim it. It does have the negative side of effect of people thinking that the memory is lost. Doing a "stack 5000000" should have released all that memory (assuming stack doesn't have some sort of upper limit). However there is a bug in one of the overlays which makes it think that it's still in use even when it isn't. This occurs when you use headers, footers, footnotes or endnotes. This has been fixed for the next update. This particular can cause a one-time loss of about 21K. There is one other system related memory problem which we have discovered related to the layers (CBM has admitted to this one). This particular problem will eventually be fixed. It doesn't lose memory permanently, but it is annoying. It can effect anywhere from 28 bytes to lots of memory (usually in the lower range). Moving windows around to different places on the screen can free some or all of it. // \X/ Lynn