Open ay2456 opened 7 months ago
Hi @ay2456
Thanks for reaching out.
This is currently the expected behaviour as we have no mechanism in place to pre-allocate memory in the case of a Out of Memory exception nor do we currently have any error persistence in place.
I should note that we do not have an item on our backlog aimed at pre allocating this memory when the server starts so that when it does go down, it would still have some memory free to use and send the report.
We currently have no ETA on this functionality. Once we have an update on this we will be sure to share the additional information here.
Are you seeing this issue often? If so then it may be worth increasing the available memory for the pod as a temporary work around.
Describe the bug
I'm running BugSnag with
celery
on Kubernetes pods. I've noticed that when the pod is out of memory with signal 9 (SIGKILL), BugSnag can't report the error:Error logs:
Environment