From 3ec3bed497b488364726c87e522c05b846ed4e70 Mon Sep 17 00:00:00 2001 From: Stefan Kost Date: Wed, 2 Mar 2011 13:00:31 +0200 Subject: monoscope: don't leak the monoscope_state data The monoscope_close() implementation was empty. --- gst/monoscope/monoscope.c | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/gst/monoscope/monoscope.c b/gst/monoscope/monoscope.c index e6e43468c..98822d322 100644 --- a/gst/monoscope/monoscope.c +++ b/gst/monoscope/monoscope.c @@ -73,8 +73,15 @@ monoscope_init (guint32 resx, guint32 resy) return stateptr; } +void +monoscope_close (struct monoscope_state *stateptr) +{ + convolve_close (stateptr->cstate); + free (stateptr); +} + guint32 * -monoscope_update (struct monoscope_state * stateptr, gint16 data[512]) +monoscope_update (struct monoscope_state *stateptr, gint16 data[512]) { /* Note that CONVOLVE_BIG must == data size here, ie 512. */ /* Really, we want samples evenly spread over the available data. @@ -155,8 +162,3 @@ monoscope_update (struct monoscope_state * stateptr, gint16 data[512]) return stateptr->display; } - -void -monoscope_close (struct monoscope_state *stateptr) -{ -} -- cgit v1.2.3