OK, I had noticed this problem from earlier versions, but never thought of reporting it. MUSHClient is leaking badly. The problem is caused by MUSHClient, no doubt about that. I checked with Resouce meter. The only way to fix it now, is just restart MUSHClient :) It has something to do with lines of input. It's ok with one world open, a bit worse with 2 worlds, and it drains my 16 MB of RAM in 10 minutes with 8 characters open fighting (you know how spammy fights are). The reason why this is obvious to me is because i only have 16 MB of RAM :) I hope you can fix it soon :) My guess would be that MC doesn't clear its lines when they leave the window correctly.
MUSHClient leaking BADLY
Posted by Poromenos on Mon 09 Sep 2002 01:40 PM — 5 posts, 18,481 views.
Are you sure it's a memory leak? When MUSHclient is initialized, there is nothing stored in the screen's output buffer. As you play, the buffer fills up until it reaches the maximum size dictated in your settings.
With multiple worlds open, this will increase your memory usage dramatically, until you have maxed all the buffers, then it should "peak", and not consume any more memory. Perhaps you don't stick around long enough during testing to monitor this?
To conserve memory, Go into your world options, and select:
...and reduce the value stored there. You can set it to the minimum of 200 lines, if you really want to conserve memory.
Also, a similar buffer is the one that stores the commands you have entered in the command box. You can edit the size of that buffer in your world options, here:
...and reduce the number there as well.
With multiple worlds open, this will increase your memory usage dramatically, until you have maxed all the buffers, then it should "peak", and not consume any more memory. Perhaps you don't stick around long enough during testing to monitor this?
To conserve memory, Go into your world options, and select:
Appearance | Output | Number of lines in output buffer:
...and reduce the value stored there. You can set it to the minimum of 200 lines, if you really want to conserve memory.
Also, a similar buffer is the one that stores the commands you have entered in the command box. You can edit the size of that buffer in your world options, here:
Input | Commands | Command History - Keep:
...and reduce the number there as well.
What you say does make sense, but i keep lines at 200, and the resources get drained after the windows fill. Also, even when they're full, resources keep diminishing. And, I usually type nothing on the alts, so command buffer doesn't justify it, it should be the same as having 1 char. What i'm trying to say is, the drain is not that immediate...
I have had reports of this before, and spent quite a bit of time looking into it. Because of the way Windows works, it is hard to say for sure how much memory is used because the amount allocated to MUSHclient seems to decrease over time if you aren't using it (as memory is swapped out to disk).
However I'll have another look. Maybe check your virtual memory settings to make sure you can use a bit more than the 16 Mb of physical RAM.
In recent versions memory is taken for "style runs", which *should* be deallocated as they are no longer required.
What does the "info" configuration tab report?
However I'll have another look. Maybe check your virtual memory settings to make sure you can use a bit more than the 16 Mb of physical RAM.
In recent versions memory is taken for "style runs", which *should* be deallocated as they are no longer required.
What does the "info" configuration tab report?
You seem to be right... It doesn't leak now with v3.26. I'm testing it out though, i should run it for an hour or two. Also, i'm not so sure the leak is in the text buffer. Might also be in a trigger (I have a trigger that matches on prompts), so that could be it. Maybe it's color handling, or I don't know what else... I'll test it and keep you posted.