Bug 14036 – Do not throw FinalizeError on OutOfMemoryError or InvalidMemoryOperationError
Status
RESOLVED
Resolution
FIXED
Severity
critical
Priority
P1
Component
druntime
Product
D
Version
D2
Platform
All
OS
All
Creation time
2015-01-24T20:15:00Z
Last change time
2015-02-18T03:38:56Z
Keywords
pull
Assigned to
nobody
Creator
dlang-bugzilla
Comments
Comment #0 by dlang-bugzilla — 2015-01-24T20:15:28Z
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.
Comment #1 by dlang-bugzilla — 2015-01-24T20:22:40Z