# Profiling memory usage in given process

**URL:** <https://forum.elixirforum.com/t/profiling-memory-usage-in-given-process/20878>\
**Category:** Questions\
**Tags:** erlang, beam, profiling\
**Created:** [March 14, 2019, 2:23pm UTC](https://forum.elixirforum.com/t/profiling-memory-usage-in-given-process/20878 "2019-03-14T14:23:12Z")\
**Posts on this page:** 1\
**Showing post:** 15

<div class="post-metadata">

**Author:** ![arnomi](https://forum.elixirforum.com/letter_avatar_proxy/v4/letter/a/e95f7d/32.png) [@arnomi](https://forum.elixirforum.com/u/arnomi)\
**Post date:** [March 18, 2019, 11:53am UTC](https://forum.elixirforum.com/t/profiling-memory-usage-in-given-process/20878/15 "2019-03-18T11:53:44Z")

</div>

> [@hubertlepicki](#):
>
> The closest thing to what I want to do would be crashing the Erlang VM

I would say, this is never necessary if you already know which process is causing the issue. As mentioned above, you can first start digging into the exact process. One thing to also look into, is garbage collection. You can use `:erlang.garbage_collect` to force garbage collection for processes. Especially if the process is long running, tuning garbage collection may be necessary.

---

_[View the full topic](https://forum.elixirforum.com/t/profiling-memory-usage-in-given-process/20878)._