Closed AkramHssaini closed 9 months ago
What is the actual panic message? And which version of Go and fasthttp are you using?
The stack call is all I get there somehow isn’t an actual message. Go and Fasthttp are all up to date
Are you sure you are on the latest Go 1.21.6? src/runtime/proc.go:398
is not a line that can panic on that version.
There should always be a message before the panic. Can you share the full output of your program?
Since the panic is so deep into the Go runtime I don't think this has anything to do with fasthttp. It seems to me like some kind of memory corruption. Are you maybe using any cgo libraries? Could it be that your system memory is broken?
You were right; the issue wasn't caused by fasthttp. It was a different package that caused the crash. Thank you a lot for the help.
When sending multiple requests with multiple threads over a long period, fasthttp crashes. I'm sending multiple requests to a server with a 'keep-alive' header, using around 100 goroutines. The program runs well for the first 30-40 minutes, but then it suddenly crashes with a stack call. I've been trying to understand it but failed. I've tried changing 'MaxConnsPerHost' and 'MaxIdleConnDuration,' but it only resulted in a bit more time before crashing. The error handling is also implemented, but fasthttp just panics, and the server is capable of responding and handling this amount of requests. I'm not able to understand what causes the issue, so I'd be glad if anyone can help me.
My configuration:
The Stackcall