Forum

Hello Hugo

I know this statement is a bit harsh and maybe not really true.. But I have noticed in last couple days that Hiawatha proccess uses a bit of memory. Before www-data proccess (Hiawatha one) would use 0.1 - 0.4 percent of total 1000MB of RAM. Now, at this moment, it's up to 7.4% and just couple hours ago it was on 5.4 so it' growing. I am not sure if there is anything I could do to test things out.. ? I do use 40M of cache via CacheSize but this is not it as I was using same setting before too..

Hiawatha version: 8.1
Operating System: Debian

I am, of course, using Hiawatha myself and haven't noticed any memory leak. What value is the RSS in the output of 'ps'? Please check the size of the cache via the CommandChannel to be sure. Otherwise, you can check for memory leaks with valgrind.

VSZ is 296524
RSS is 110792

Still growing after last night, now at 10.7%

I will check valgrind and let you know..

Can you show me your configuration file? I'd like to see what features you are using. Perhaps the leak is in a feature I'm not using.

Here it is http://paste.pocoo.org/show/585165/

CacheMaxFileSize is 256 after all, could this be issue ? (but I 've been using this config forever, only thing I changed recently was url toolkit for expires )

I don't see anything enabled feature in the configuration file that I don't use. Please, try running Hiawatha via valgrind for a while and see what it says. Tip: use the screen tool and run Hiawatha with the -d parameter.

I am not sure what ./hiawatha stands for on that valgrind howto ?

In means 'running Hiawatha from the current directory'. It assumes that you use a non-stripped binary in the current directory, which you just compiled.