Request errors out and kills instance with "The process handling this request unexpectedly died"

[Jeremy D]

I have an endpoint that accepts a date range. A short date of a year returns data fine. More than a few years, it takes about 25 seconds or so before returning a 500 error with no response in the body, but in Logging, I see this:

"The process handling this request unexpectedly died. This is likely to cause a new process to be used for the next request to your application. (Error code 203)"

This seems to also kill the instance that the request was ran on, and spins up another. This means a user could potentially continue to try and make this same request and have it constantly killing and restarting instances, slowing down response times everywhere else.

Is there a way to get more details about whats going wrong here? 

[Jeremy D]

Some further investigation, trying this on a separate test version using F4_HIGHMEM (we normally run F4), I can see the instance increase in memory usage dramatically until it reaches 1GB, and then it errors out/kills the instance. So, it would seem this is a memory limitation. I thought there were other sort of "fail safes" in the event the instance uses too much memory?

[Olu]

This is really interesting. I recommend that you report this issue on the issue tracker link[1][2] as a Google Cloud Engineer will be able to assist you by examining exactly why the memory usage is observed on your application Endpoint. Or better still, open a case with the Google Cloud Platform Support team.  Certainly, there are limits that apply to resources made available to your applications. The Support engineers will be able to provide specific information in relations to your Project. 

[1]https://issuetracker.google.com/

[2]https://cloud.google.com/support/docs/issue-trackers#trackers-list

[3]https://cloud.google.com/support/