Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Currently, the allocator close throws an exception that includes some details in case of memory leaks. However, if there is a hierarchy of allocators and they are all closed at different times, it's hard to find the cause of the original leak.
If we also log a message when the leak occurs, it will be easier to correlate these.
Attachments
Issue Links
- links to