That suggests it is a malloc leak of consistently sized objects (i.e. we are leaking one particular type of fixed-size object). What is your usage pattern - what particularly aggravates the leak? Chromium, firefox, libreoffice, totem, etc?
That suggests it is a malloc leak of consistently sized objects (i.e. we are leaking one particular type of fixed-size object). What is your usage pattern - what particularly aggravates the leak? Chromium, firefox, libreoffice, totem, etc?