:
> Because they are tracked separately. See allocSpan() in mheap.go.
>
> On Mar 27, 2022, at 11:50 AM, Shlomi Amit wrote:
>
> Thank Robert.
> My C code does call back Go code, but no recursion there.
> If stack allocations are part of the heap, why it is not reflected in
>
hrink under certain conditions.
>
> Since they are allocated on the heap, you may be encountering a situation
> where you are extended the stack to a degree that the GC cannot keep up
>
> On Mar 26, 2022, at 4:01 PM, Shlomi Amit wrote:
>
> I've already checked process
sibly using
Valgrind? Can I use it to profile my Go application with Cgo?)
On Sat, Mar 26, 2022, 22:54 robert engels wrote:
> Are you certain your CGo code isn’t creating threads?
>
> On Mar 26, 2022, at 1:10 PM, Shlomi Amit wrote:
>
> Yes. I already monitoring the runtime st
. See https://tpaschalis.github.io/goroutines-size/
>
> On Mar 24, 2022, at 3:18 PM, Shlomi Amit wrote:
>
> Hi.
>
> I’m trying to find a memory leak in my application.
> I’ve added some runtime memory stats to the logs (Heap & Stack stats.. go
> routine and heapObject coun
