You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 19, 2021. It is now read-only.
We’re getting very occasional hits against memory limit boundaries. Very rare, most return result 200, however 2 returned status 500. It would be good to profile the memory use to make sure we’re well within limits.
"Exceeded soft private memory limit of 128 MB with 186 MB after servicing 564 requests total"
"While handling this request, the process that handled this request was found to be using too much memory and was terminated. This is likely to cause a new process to be used for the next request to your application. If you see this message frequently, you may have a memory leak in your application."
We’re getting very occasional hits against memory limit boundaries. Very rare, most return result 200, however 2 returned status 500. It would be good to profile the memory use to make sure we’re well within limits.
Sample:
2015-05-04 15:03:43.301 /getFile 200 3982ms 7328kb module=default version=01060000p
2015-04-27 14:34:11.320 /getFile 500 4150ms 0kb module=default version=01060000p
2015-04-06 14:00:53.791 /postMessage 200 159ms 0kb module=default version=01060000p
2015-03-31 15:09:52.026 /postMessage 500 1951ms 0kb module=default version=01060000p
"Exceeded soft private memory limit of 128 MB with 186 MB after servicing 564 requests total"
"While handling this request, the process that handled this request was found to be using too much memory and was terminated. This is likely to cause a new process to be used for the next request to your application. If you see this message frequently, you may have a memory leak in your application."