Can you show us the output starting from the very beginning? There is some information missing, and it matters. You can omit the application code from the stack trace, that is probably not useful. Thanks.

Fuzzing QueryEscape might surface a reproducer, if that hasn't been tried...

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@tomdeering-wf please take a look at Ian's request in #38643 (comment), the whole trace helps us out and currently we can't act on this issue.

@networkimprov great idea, indeed that seems like the sensible way to find out, would you like to handle that?

Tried this with 1.13.3 on linux/amd64, saw no panic. Maybe memory corruption?

package main

import (
   "net/url"
   "fmt"
)

func main() {
   fmt.Println("4 byte")
   for a := 0; a <= 255; a++ {
      if (a+1) % 8 == 0 { fmt.Println(a) }
      for b := 0; b <= 255; b++ {
      for c := 0; c <= 255; c++ {
      for d := 0; d <= 255; d++ {
         _ = url.QueryEscape(string([]byte{byte(a),byte(b),byte(c),byte(d)}))
      }}}
   }
}

Hi folks, sorry for the delay. Unfortunately I've lost the context beyond what is captured in this issue. We saw this happen just once in one of our cloud environments, and I also am unable to repro locally.

I thought I'd captured all the pertinent info from the stack, sorry Ian. If I'm able to relocate that panic, I'll post back with more info.

@ianlancetaylor found it. So, the stack above that was application code catching the panic and re-panicking. The subject of the panic was runtime error: index out of range [59802754] with length 59802754, which seems to have come out of the line t[j+2] = "0123456789ABCDEF"[c&15]. You're right, that does seem very relevant, sorry for the omission 🤦‍♂️

Thanks. Are you parsing URL values that are 59802754 bytes long?

From looking at the code I don't see how this panic could happen other than memory corruption, but I may be missing something.