Results 738 comments of Andrew King

@Dinth What is the architecture of your Portainer machine? Can I build just the x86_64 or am I going to need to go the extra mile and build arm as...

Ok so the docker will be here (in half an hour) ```bash docker pull quantumentangledandy/neolink:test-valgrind ``` The binding of the config and ports are the same as usual BUT there...

P.s. the docker build succeeded. Please run when you can and post the massif.out when you can

This is the memory profile of that massif.out

That sigterm is expected. It's the way the `timeout` command signals the app to stop. Nothing wrong with it at all

Can you try pulling latest master branch of the docker? Perhaps something very recent fixed it.

Nope will be single process. Even if children were spawned valgrind would track them too. There are two main changes here - ulimit -n 1024 - using the debug build...

I could try to run valgrind on the release build. It will just make figuring out what is wrong much harder without the debug symbols

Anyways I'm off to sleep now so I'll do that tomorrow

I'm building the realease version of the valgrind docker here https://github.com/QuantumEntangledAndy/neolink/actions/runs/8624926076 should be ready soon