-
Args:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0xa6a67f]
goroutine 6 [running]:
github.com/jackc/pgx…
-
经过半年的改进，目前关闭 handleLoop 的改进已经接近尾声，目前针对一个网络连接已经能够做到：
1 只有一个 read goroutine 专门处理读请求；
2 在业务处理逻辑的 goroutine 中同步处理写请求。
这个处理方法能否大幅度减少网络连接相关的 goroutine 的数量，在处理小包[= 8MiB] 的情况下，还是有很大概率会失败，其本质是 tcp/udp 的发…
-
github.com/klauspost/compress/zstd Encoders and Decoders leak goroutines if they're garbage collected without calling Close on them first (like sync.Pool does). It's probably not important here, but F…
-
## Enhancement
github.com/pingcap/tidb/pkg/store/copr.(*copIteratorWorker).run will always do the ```runtime.newstack``` and it will take many time on it. so we can use goroutine pool to resolve it…
-
```./spray_linux_amd64 -l all_target.txt --bak --common > output.txt```
```
panic: runtime error: invalid…
-
Extism continues to be a delight to work with.
I realized that Extism probably has limited support for automatic concurrency, especially when calling host functions or the HTTP API. I verified that…
-
I think it happened when I was restarting RocketPool eth1 to add a command line option.
hyperdrive_cs_daemon | panic: runtime error: invalid memory address or nil pointer dereference
hyperdrive_c…
-
During https://github.com/nspcc-dev/neo-go/pull/3582#issuecomment-2395164230
I have created the pool:
```
signer := user.NewAutoIDSignerRFC6979(acc.PrivateKey().PrivateKey)
p, err := pool.New(poo…
-
Hi,
After upgrading to new version, index-api get panic:
```
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x20 pc=0…
-
**Describe the bug**
After releasing all conns back to a `pgxpool.Pool` and closing the pool, there can still be goroutines left running. That's because `triggerHealthCheck` gets called upon `Release…