Customer is experiencing pod crashes on Orders-API in their Production and they believe they're related to the Golang MongoDB driver version 1.15. I'm reaching out to inquire if there is any known bug or issue related to Golang MongoDB driver version 1.15 that could lead to pod crashes on their API.
They have recently performed:
1. Go driver upgrade from 1.10 to 1.15 on the 7th of May 2024.
2. DB upgrade from 5.0.18 to 6.0.14 on the 19th of May 2024.
Here's a snippet from their stack trace:
```
unexpected fault address 0x5700be60
fatal error: fault
[signal SIGSEGV: segmentation violation code=0x1 addr=0x5700be60 pc=0x4790e9]

goroutine 130204602 gp=0xc00684d180 m=2 mp=0xc000082808 [running]:
runtime.throw(

)
/usr/local/go/src/runtime/panic.go:1023 +0x5c fp=0xc00138ab18 sp=0xc00138aae8 pc=0x43d79c
runtime.sigpanic()
/usr/local/go/src/runtime/signal_unix.go:895 +0x285 fp=0xc00138ab78 sp=0xc00138ab18 pc=0x4561e5
runtime.memmove()
/usr/local/go/src/runtime/memmove_amd64.s:399 +0x489 fp=0xc00138ab80 sp=0xc00138ab78 pc=0x4790e9
go.mongodb.org/mongo-driver/x/bsonx/bsoncore.appendstring(...)
/go/pkg/mod/go.mongodb.org/mongo-driver@v1.15.0/x/bsonx/bsoncore/bsoncore.go:805
go.mongodb.org/mongo-driver/x/bsonx/bsoncore.AppendString(...)
/go/pkg/mod/go.mongodb.org/mongo-driver@v1.15.0/x/bsonx/bsoncore/bsoncore.go:163
go.mongodb.org/mongo-driver/bson/bsonrw.(*valueWriter).WriteString(0xc000531d60,

)
```
Please see attached Supporting Stack Trace and the log leading up to the crash pricecrash.txt