“stuck”)
> and review that. Or maybe use an external sampler like ‘Instruments’ on osx,
> or similar. It certainly seems like some routine is spinning - prevent GC
> from happening and pausing everything else.
>
>> On Dec 12, 2018, at 5:20 PM, Eric Hamilton > <mailto:e.
on’t have an incorrect highly recursive
>>> loop that is causing the stack marking to take a really long time… ?
>>>
>>>
>>>> On Dec 11, 2018, at 8:45 PM, Eric Hamilton >>> <mailto:e...@kasten.io>> wrote:
>>>>
>>>> Of
Of course. (I forgot about that option and I'd collected those traces at a
time when I thought I'd ruled out GC-- probably misread MemStats values).
Here's the gctrace output for a repro with a 5.6 second delay ending with
finish of gc17 and a 30+ second delay ending in SIGTERM (which coincides
