Concurrent request ends up in runtime memory error

[karthikpdc]

If i run any base image in docker it crashes when a concurrent request is made. In AWS environment it will create new instance to handle the request but here there will be only one instance so it will not handle the other request but it should return graceful error instead of runtime error and crashing the container.

Steps to reproduce. Just follow these steps to create a basic image and run it in docker container.

Make concurrent request to invoke your function then the container will crash with below runtime error.
(rapid) ReserveFailed: AlreadyReserved panic: runtime error: invalid memory address or nil pointer dereference [signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0x6af115] goroutine 62 [running]: go.amzn.com/lambda/rapidcore.(*Server).Invoke.func2() /LambdaRuntimeLocal/lambda/rapidcore/server.go:666 +0xf5 created by go.amzn.com/lambda/rapidcore.(*Server).Invoke /LambdaRuntimeLocal/lambda/rapidcore/server.go:649 +0x23d

[jmehnle]

This is really aws/aws-lambda-runtime-interface-emulator#97.