Hi, I would like to know how to identify mapping between an OS thread and
go-routine from the stack trace i.e. which go-routine is scheduled for
execution on a OS thread.
*Background:* My application spawns very large number of go-routines (upto
2M) for heavy data processing. In some cases, I a
Looking at all goroutines with runnable state seem to be the solution but I
am not very sure about this.
*goroutine 15825281 [runnable]*
On Tuesday, January 12, 2021 at 9:16:47 PM UTC+5:30 varun...@gmail.com
wrote:
> Hi, I would like to know how to identify mapping between an OS thread
@Ian,
This statement is a bit confusing to me regarding HeapInuse: "*which
includes space allocated to hold objects that do not yet exist or that have
been released by the garbage collector*"
According to memstats documentation, HeapInUse -> Includes all spans that
have at least one object in
heap -> manual spans)?
Is it always the case that StackInUse is shown in heap profile ?
Thanks,
Varun
On Wednesday, May 26, 2021 at 1:24:32 AM UTC+5:30 Ian Lance Taylor wrote:
> On Tue, May 25, 2021 at 6:53 AM varun...@gmail.com
> wrote:
> >
> > This statement is a bit c
(Sorry for the typo. Where ever I mentioned alloc -> heap, I mean all ->
heap)
On Wednesday, May 26, 2021 at 3:01:21 PM UTC+5:30 varun...@gmail.com wrote:
> Thanks @Ian for the clarification.
>
> The BySize arrays gives the number of active objects in a size class but
> it
Hello,
Recently we have been seeing multiple occurrences of "fatal: morestack on
gsignal" error in our system tests. The issue happens with golang 1.13.7
and golang 1.16.5 runtimes. The process restarts after this error and no
stack trace is dumped. Our process uses CGO calls, I/O ops etc.
So
SEGV in CGO layer
and that is being returned as SIGTRAP by runtime.
I am still clueless as to why a process can crash with "morestack on
gsignal". Any pointers to debug this further would be of great help.
Thanks,
Varun
On Wednesday, September 1, 2021 at 2:44:52 PM UTC+5:30 varun...@
likely already been fixed.
>
> On Thu, Sep 9, 2021 at 4:15 AM varun...@gmail.com
> wrote:
>
>> Minor update:
>>
>> a. The crash with "morestack on gsignal" happens to be independent of the
>> kernel versions mentioned earlier
>> b. We implemen
