Skip to content

Memory leak: RingBuffer::~RingBuffer() is never called #23

@feoff3

Description

@feoff3

Hey, I have found a memory leak inside the code during my test.

Ring buffer is created in MiniportWaveRTStream via new() which calls RingBuffer constructor and then allocates some memory.

After that RingBuffer::~RingBuffer() descructor is never called (so to free memory associated with RingBuffer)

adding delete m_RingBuffer (instead of pool free) to MiniportWaveRTStream destructor, or adding separate presudo-desctructor function (e.g. Deinit() ) to RingBuffer class, and then calling it from MiniportWaveRTStream will fix the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions