// thus on Tue, 16 Jun 1998 00:19:29 +0000, Chuck wrote:
> Is the following scenario a memory leak:
> Using ps, the mud's memory usage is 2772 (RSS 2300)
> I then loaded about 24 mobs using 'load mob'
> Using ps, the mud's memory now read 2776 (RSS 2300)
> I then purged the room with 'purge'
> Using ps, the mud's memory still read 2776
> I then loaded about 20 more mobs and the mem stayed at 2776.
> Is this normal behavior?
Alloc'ed memory via malloc(3) normally when free(3)'ed doesn't return to
the system. It's set aside for future use by that same program (and not
returned to the system). There are a couple implementations of memory
allocation that do return memory, but normally it isn't worth it.
Developement packages like purify[1] can analyze leaks or by using a malloc
package like gc[2]. A memory "leak" is normally suspect when you leave
your mud running for a period of time while "idle", and over any hour it
continuously increases in size w/o an explicable reason.
d.
[1] http://www.pure.com
[2] http://reality.sgi.com/boehm/gc.html
+------------------------------------------------------------+
| Ensure that you have read the CircleMUD Mailing List FAQ: |
| http://democracy.queensu.ca/~fletcher/Circle/list-faq.html |
+------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 12/15/00 PST