monitor container OOM killed with recommended resource

[WeihanLi]

Hi team, we're using the dotnet-monitor as sidecar in k8s, and we get some OOM from the monitor container, which caused the pod restarts

The resource for dotnet-monitor container is the same as the sample

dotnet-monitor/samples/AKS_Tutorial/deploy.yaml

Lines 55 to 61 in 3f005f5

	resources:
	requests:
	cpu: 50m
	memory: 32Mi
	limits:
	cpu: 250m
	memory: 256Mi

    resources:
      limits:
        cpu: 250m
        memory: 256Mi
      requests:
        cpu: 50m
        memory: 32Mi

I have some questions about the dotnet-monitor container:

1. Would a dump file be generated when the dotnet-monitor OOM or exited unexpectedly in other scenes?
2. What may cause the dotnet-monitor sidecar OOM? How should we consider a suitable memory resource for our usage? We're using the default config without additional metrics or other things