Hi,
zimoun writes:
> Hi,
>
> On Mon, 07 Nov 2022 at 12:03, Ludovic Courtès wrote:
>
>> --8<---cut here---start->8---
>> scheme@(guile-user)> (profile-heap)
>
> [...]
>
>> sampled heap: 3.48865 MiB (heap size: 12.78906 MiB)
>> $5 = #t
>> --8<---cut
Hi,
On Mon, 07 Nov 2022 at 12:03, Ludovic Courtès wrote:
> --8<---cut here---start->8---
> scheme@(guile-user)> (profile-heap)
[...]
> sampled heap: 3.48865 MiB (heap size: 12.78906 MiB)
> $5 = #t
> --8<---cut here---end--
Hello Guilers,
While desperately chasing <https://issues.guix.gnu.org/59021> and
related memory leak issues, I came up with the attached rudimentary heap
profiler. You can load it and invoking it in a running process:
--8<---cut here---start->
Hello!
Andy Wingo writes:
> To really track this down we need a heap profiler. To make a heap
> profiler, we need to hack libgc.
As a start, I suggest looking at these:
-
http://thread.gmane.org/gmane.comp.programming.garbage-collection.boehmgc/3392
- “Understanding Memory alloc
