Re: Application doesn't leak memory running valgrind

On Mon, 2022-02-28 at 18:00 +0100, Floyd, Paul wrote:
> On 2022-02-28 17:28, Stefano Antonelli wrote:

> I don't know much about Qml. Does this use any sort of memory manager
> or
> garbage collector?

Qml is built on top of javascript.  There is definitely a garbage
collector.

> One thing that you could try is to run your application with
> --tool=massif and then repeat the run but add --pages-as-heap=yes. If
> there is a big difference in the two then it means that your
> application
> is using a memory pool not based on malloc. Use ms_print (or
> massif-visualizer) to see the massif profiles.

There is a huge difference.  1MB vs 90MB.

Using a memory pool doesn't explain why the leak doesn't get bigger
when running valgrind though does it?

And thanks for the help!

-Stef