https://issues.dlang.org/show_bug.cgi?id=14036
Issue ID: 14036 Summary: Do not throw FinalizeError on OutOfMemoryError or InvalidMemoryOperationError Product: D Version: D2 Hardware: All OS: All Status: NEW Severity: critical Priority: P1 Component: druntime Assignee: nob...@puremagic.com Reporter: thecybersha...@gmail.com We should not attempt to throw FinalizeError when an InvalidMemoryOperationError is thrown in the destructor. This will only throw a second InvalidMemoryOperationError. Ideally, we should not catch it at all, so it is possible to see the stack trace of the destructor which caused the InvalidMemoryOperationError. --