Wt

We use valgrind to verify that Wt (or the applications we develop with Wt) has no memory leaks. On a clean shutdown of the Wt application (with fcgi this is done e.g. by shutting down the http server), Wt will invoke the destructor of all application objects, free all other memory it allocated, and you should have no leaks in the valgrind report (some of the dependency libraries may have a small leak, but that should be constant and not grow with the number of sessions, ...).

Looking at the output of top or ps is a flawed way to check if memory is freed or not. Many implementations of malloc() cache memory for later use, so they don't return it to the OS when you call free(). Even without memory leaks, top may report a significant memory use.

BR,

Wim.