Mike Cohen

How can we detect this condition? If the service is stopped then the process is killed and we can not communicate to the server any more. You can tell outside...

As a workaround we can use this flag instead; `--config.frontend-artifact-definitions-directory=`

Fixed by #2098

There is a nanny in the client that kills the process if it uses too much memory or fails to connect to the server (for example if due to a...

Sometimes when you do a heavy hunt that transfers a lot of data it takes a while for the query to run. The client tries to limit the impact on...

Were you able to kill the client remotely with killkillkill() ? If this happens again it would be useful to try to get a profile if you can easily reproduce...

You can collect profiles as described here https://docs.velociraptor.app/knowledge_base/tips/debugging_clients/ https://docs.velociraptor.app/blog/2020/2020-08-16-profiling-the-beast-58913437fd16/

It is not necessarily a leak - it might just be that it is building up to its constant memory usage over time (filling caches etc) so unless it is...

Ok please attach the profile information containing the heap output and metrics

Can you give a more actionable suggestion? What exactly is the issue? How can we improve it? It is unlikely that we will rewrite the GUI from scratch in a...