I have been working with SCI Studio 2.12 today, and have been able to pin down where the memory loss problems exactly are. I turned on my resouce monitor and ran SCI Studio then I went to work on some scripts, the resource monitor kept showing a loss in percentages while the script editor was open. When I closed the script editor the loss stopped. But the memory didn't come back until I closed SCI Studio. Something in your script editor is draining the memory.
The bad news is that it's beyond my control. I inspected it with the resource monitor, and discovered that Borland's VCL (the library used for all the GUI) isn't fully freeing the windows/controls. I created a simple two window application to confirm this, and it's true. I then discussed it with others using Borland's VCL, and they too, have the problem. The only way to free the memory is to close the program, then open it again. Win9x users may need to reboot! This is horrible! I'd switch it to another library, but it's got over three years of work in it, and it would invlove rewriting virtually the entire program.
XP/2000 (NT) can handle these leaks fine, but 9x (DOS) I guess can't.
The worst thing is that examining plain/empty Borland C++Builder VCL apps with the resource monitor, I've discovered that it takes up more memory that isn't freed just my moving/resizing the window, or even switching from the resource monitor back to the app. Now, when programs like SCI Studio have hundreds of controls/windows being created/moved/resized, it causes serious problems!
I started disliking Borland C++Builder a little while ago due to it's bugs, but now I REALLY dislike it!