Bug #274: Various memory leaks
| ID | #274 |
|---|---|
| Submitter | Sausage |
| Product | EOSERV |
| Severity | Normal |
| Status | CLOSED, INVALID |
| Submitted | 1st Feb 2014 |
| Updated | 9th Apr 2016 |
10 years, 13 weeks ago
Many small objects are allocated and never freed.
Most should be replaced with non-reference types, and other cases should be covered with smart pointers.
Goal is to never assign the result of new to a raw pointer.
Comments
8 years, 3 weeks ago
There are no known memory leaks in EOSERV at present, and no evidence of any wide-spread problems.
Admin reload commands may still need to be looked at.
Updated Status to CLOSED, INVALID
Add Comment
Please don't post unless you have something relevant to the bug to say.
Do not comment to say "thanks" or "fix this please".
Please log in to add comments. EOSERV Bug Tracker > Bug #274: Various memory leaks