are you running any hashtables?
i noticed they have a similar effect
when you load a large hashtable, and it grows, it grows in the memory as well. however when you save the grown hashtable, restart mirc and load the new table, the size in memory wont be the same.
not sure if this is a memoryleak or just optimization.
