Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
ffmpeg
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
Show more breadcrumbs
Luma Media Server
ffmpeg
Commits
e518cb86
Commit
e518cb86
authored
12 years ago
by
Paul B Mahol
Committed by
Luca Barbato
11 years ago
Browse files
Options
Downloads
Patches
Plain Diff
jvdec: Fix memory leak of jv->frames
Signed-off-by:
Luca Barbato
<
lu_zero@gentoo.org
>
parent
027712e8
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
libavformat/jvdec.c
+10
-0
10 additions, 0 deletions
libavformat/jvdec.c
with
10 additions
and
0 deletions
libavformat/jvdec.c
+
10
−
0
View file @
e518cb86
...
...
@@ -59,6 +59,15 @@ static int read_probe(AVProbeData *pd)
return
0
;
}
static
int
read_close
(
AVFormatContext
*
s
)
{
JVDemuxContext
*
jv
=
s
->
priv_data
;
av_freep
(
&
jv
->
frames
);
return
0
;
}
static
int
read_header
(
AVFormatContext
*
s
)
{
JVDemuxContext
*
jv
=
s
->
priv_data
;
...
...
@@ -229,4 +238,5 @@ AVInputFormat ff_jv_demuxer = {
.
read_header
=
read_header
,
.
read_packet
=
read_packet
,
.
read_seek
=
read_seek
,
.
read_close
=
read_close
,
};
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment