aws / aws/aws-lambda-runtime-interface-emulator

Runtime error: invalid memory address or nil pointer dereference

未关闭
#97 24 条评论 27 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Go
星标
1.1k
派生
118
平均合并
42 分钟
30 天内合并 PR
2

描述

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

贡献指南

打开贡献指南

调研方向

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.

由索引模型根据 Issue 内容生成。

评估

技术栈
go
领域
backend
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
冷清
描述清晰度
基本清楚
新手友好度
45/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。