Feels like a memory leak to me. I would look for growing heap size in the gc
logs. I am guessing that the system is not completely hung - but rather the
runtime is having a hard time obtaining more memory, so it is slowing the
allocators to a rate that makes them appear hung.
It may be that the
This is an odd one. For reference, this is a customer machine, Windows
server 2016, compiled with go1.20.11. The application just hangs after a
number of days; windows minidump reveals that most threads are doing this:
Goroutine 462 - User: unicode/utf16/utf16.go:106 unicode/utf16.Decode
(0xe
Did you ever figure this out? I am hitting the same issue, and it's quite
frustrating :(
On Monday, July 25, 2022 at 2:08:18 AM UTC-7 santhoshth...@gmail.com wrote:
> Hi Everyone
>
> I am importing the proto of other project into my proto file and run
> protoc command.
> I got this below error
