Just created the mother of all memory leaks, 300MB/s :|

It's a memory geyser 😁

Show me your ways

Nice. Which technology and how?

C# with Magick.net, it's resizing, trimming images with proper multithreading. Haven't had time to narrow it down further as I had to leave for home just after discovery.

Even with 32GB ram it's pretty fast in filling that.

That's way faster than my internet.

@creator yeah sorry, fiber internet and a high end cpu/ram/ssd combo will fuck up your day pretty fast....

End result, getting the pixel collection and forgetting to dispose it is an understandable memory leak.

Is it a real leak in a technical way, or is it just the gc not knowing the real size of the data?

In some imaging libraries, the image data is in unmanaged memory and thus the managed object itself is only a few bytes with a handle. The gc may even dispose the data with the objects finalizer, but it can't know that a few small objects in memory are linked to gigabytes of data, so it may keep them alive longer than required.
Enforcing gc is normal when working with that kind of library.

Looke like leak, imagemagick uses a native library and the scope of the leak is just a few lines in a sepdrate function, so if it were disposable the GC would do so every few seconds but it doesn't.

Using the proper dispose/using statement remedies it completely.