Bug 95348 - Possible memory leak in memtrap.c
Summary: Possible memory leak in memtrap.c
Status: RESOLVED MOVED
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: core (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-11 03:46 UTC by Sachin Kumar Chauhan
Modified: 2018-07-30 10:30 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Sachin Kumar Chauhan 2016-05-11 03:46:05 UTC
In src\pulsecore\memtrap.c, a pointer aupdate is allocated memory using pa_aupdate_new() but pa_aupdate_free() is never called to free the memory.

Is the alloted memory being leaked ?
Comment 1 Arun Raghavan 2016-05-13 10:05:06 UTC
(In reply to Sachin Kumar Chauhan from comment #0)
> In src\pulsecore\memtrap.c, a pointer aupdate is allocated memory using
> pa_aupdate_new() but pa_aupdate_free() is never called to free the memory.
> 
> Is the alloted memory being leaked ?

This is one-time statically allocated memory and is not freed until the program exits. That is why you don't see an explicit free.

That said, it might be possible (and even desirable) to not have this code path executed in the memfd case. CC'ing Ahmed Darwish to see if he has something to add there.
Comment 2 GitLab Migration User 2018-07-30 10:30:18 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/471.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.