[nfbcs] locating hard to find memory leaks

[Littlefield, Tyler]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello all,
I am working on my mud engine:
http://github.com/sorressean/aspen
There appears to be a really weird issue when
serializing/deserializing a lot of data. When the data is loaded, I
end up increasing my memory to hold a 250x250 grid of rooms and exits
from 100 KB to around 500 MB. I'm using TinyXML for this.
Does anyone have any ideas in terms of how to track this down? Running
valgrind doesn't seem to produce any results. This shouldn't be using
this much memory at all--the objects are compact, which you can
understand if you can hold 65000 rooms plus exits in memory. Any tips
here would be awesome. Also if you're interested in a run, I provided
a world generated grid here:
https://dl.dropboxusercontent.com/u/10204868/wilderness.tgz
to use after you clone aspen:
mkdir -p aspen/data/areas
put the extracted wilderness file there and run.
Any tips/advice would be greatly appreciated.
Thanks,
- -- 
Take care,
Ty
twitter: @sorressean
web:http://tysdomain.com
pubkey: http://tysdomain.com/files/pubkey.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBAgAGBQJWJmG+AAoJEAdP60+BYxejZt4H/0wXby2sRfzG/MbssA52K3I7
YKFxLfKGwgdPOG0ADrME2rv19z/lIWEPewI7uwYuQiQZydVsF4FAOQeghj4vnqjZ
V7xMADTatlvmM3cznpmsg+JAtIW3XYhZq62halnTA15XVJFna5wDtLr6BZbQdGhC
R84QYqQi6JmyM1idQQS9Q9k47xGGVkT9v8GR2pkzbnCemy8QhqTdoTAUbvFg4l/U
CRr1PCbt31lsgCir8dqPzH6gx/+ujn812WCOhXJTTm93gTF5uUVR8x6wYeBz0w1g
c9OyhmmMVa1LhwdoGHl7nOoJa/OIldaNl/8psAc1AQ5kIP+aKgJUDsiYWUtdQ3U=
=kDiq
-----END PGP SIGNATURE-----