Memory Leak

Open
#182 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
50/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
c
Domain
performance

Research direction

Start at the allocation around line 1077 and the entrypoints reference around line 1139 in encode/h264encode.c. Trace the ownership and cleanup paths for entrypoints, then verify that the reported allocation is released on every relevant path and that the encoder tests still pass.

Written by the indexing model from the issue text.

Description

Dominant language
C
Stars
244
Forks
175
Avg merge
9d 7h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from intel/libva-utils

All issues in intel/libva-utils

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.