Skip to content

Memory leak detection #17

@GoogleCodeExporter

Description

@GoogleCodeExporter
There doesn't seem to be good memory leak detection (or any at all). 
What would be nice is if there's a way to save the heap and stack memory
address before the test, and then compare the heap and stack memory
addresses after end of the test fixture and check for any memory leaks.
This doesn't seem to be happening.


Original issue reported on code.google.com by ray...@gmail.com on 17 Jul 2008 at 8:35

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions