aws / aws/aws-lambda-runtime-interface-emulator
Runtime error: invalid memory address or nil pointer dereference
- Dominant language
- Go
- Stars
- 1.1k
- Forks
- 118
- Avg merge
- 42m
- Merged PRs (30d)
- 2
Description
The following error occurs when executing several simultaneous requests:
----
19 Jun 2023 22:05:39,909 [INFO] (rapid) ReserveFailed: AlreadyReserved
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x68c30f]
goroutine 131 [running]:
go.amzn.com/lambda/rapidcore.(*Server).Invoke.func2()
/LambdaRuntimeLocal/lambda/rapidcore/server.go:653 +0xef
created by go.amzn.com/lambda/rapidcore.(*Server).Invoke
/LambdaRuntimeLocal/lambda/rapidcore/server.go:636 +0x23d
----
Docker image: public.ecr.aws/lambda/python:3.8
Contributor guide
Research direction
Start with the stack trace in rapidcore/server.go around lines 636 and 653, then reproduce the failure with several simultaneous requests using the public.ecr.aws/lambda/python:3.8 Docker image. Trace the ReserveFailed: AlreadyReserved path and verify that concurrent requests no longer cause an invalid memory address or nil pointer dereference panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100