openframeworks / openframeworks/openFrameworks

ofVideoPlayer on Raspberry Pi remains in memory after destruction

Open
#4,891 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
10.4k
Forks
2.6k
Avg merge
1d 21h
Merged PRs (30d)
9

Description

I am building an application for the Pi where I create a new video player and destroy the old one every now and then. Even though I am destroying the previous video player the memory usage keeps growing.

Here is the create code:

_video = new ofVideoPlayer();
_video->load(fileName);
_video->setLoopState(OF_LOOP_NORMAL);
_video->play();

Destroy code in the destructor:

_video->stop();
_video->close();
delete _video;

Contributor guide

Open the contributing guide

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.

Research direction

Start with the shown ofVideoPlayer creation and destructor paths, reproducing repeated load, play, stop, close, and delete cycles on Raspberry Pi while monitoring memory. Trace the player lifecycle to identify what remains allocated after destruction; done means repeated replacement no longer causes memory usage to grow.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, raspberry-pi
Domain
embedded-iot
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.