MS if app-server crashes due to OOM (or whatever caused issue #335), some indication of crash type is at least logged (if possible)

[Venryx]

Basic steps:

• Create a test-case somewhere that causes app-server's memory usage to exceed the memory limit (I guess, just intentionally create a large memory leak that keeps growing), and confirm whether a memory-limit violation causes an "no error message" crash.
• If it does cause that, then find a way to log a specific error message confirming when a crash is due to exceeding a memory limit. (this way we can tell between "simply memory limit" sudden crashes, and sudden crashes of another type)