starred/ccextractor
1
0
Fork 0
mirror of https://github.com/CCExtractor/ccextractor.git synced 2026-02-15 21:23:10 +00:00
Code Issues 1.5k Packages Projects Releases 20 Wiki Activity

Memory Leak: File buffer not freed, leaking 16MB per demuxer instance #897

New Issue
Closed
opened 2026-01-29 16:56:28 +00:00 by claunia · 1 comment
claunia commented 2026-01-29 16:56:28 +00:00
Owner
Copy Link

Originally created by @THE-Amrit-mahto-05 on GitHub (Jan 7, 2026).

Description

Discovered a memory leak in CCExtractor: the file buffer allocated by the demuxer is never freed. This results in approximately 16MB of memory being leaked for each demuxer instance.

Steps to Reproduce

  1. Run CCExtractor on a video file.
  2. Observe memory usage of the process.
  3. Repeat with multiple files or instances.
  4. Memory usage continues to grow and is not released.

Impact

  • Long-running or batch operations can consume large amounts of memory.
  • Could cause crashes or slow performance on low-memory systems.
  • This is a real, current issue affecting stability, not a futuristic concern.

Suggestion

  • Free the allocated file buffer after demuxing completes.
  • Add tests to verify that buffers are properly released.
Originally created by @THE-Amrit-mahto-05 on GitHub (Jan 7, 2026). ### Description Discovered a memory leak in CCExtractor: the file buffer allocated by the demuxer is never freed. This results in approximately 16MB of memory being leaked for each demuxer instance. ### Steps to Reproduce 1. Run CCExtractor on a video file. 2. Observe memory usage of the process. 3. Repeat with multiple files or instances. 4. Memory usage continues to grow and is not released. ### Impact - Long-running or batch operations can consume large amounts of memory. - Could cause crashes or slow performance on low-memory systems. - This is a real, current issue affecting stability, not a futuristic concern. ### Suggestion - Free the allocated file buffer after demuxing completes. - Add tests to verify that buffers are properly released.
claunia commented 2026-01-29 16:56:29 +00:00
Author
Owner
Copy Link

@cfsmp3 commented on GitHub (Jan 8, 2026):

Please don't open a ticket for these things - PRs are OK, but issues are for users to report problems. If a developer sees a problem he/she just sends a PR.

@cfsmp3 commented on GitHub (Jan 8, 2026): Please don't open a ticket for these things - PRs are OK, but issues are for users to report problems. If a developer sees a problem he/she just sends a PR.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
CEA-708
difficulty: easy
difficulty: hard
difficulty: medium
DTMB
DVB
enhancement
enhancement
Flutter GUI
GCI19
good-first-task
GSoC 2021
GSOC-2023
GSOC-2023
GSOC-2023
GSoC-related
Hacktoberfest
HardsubX
help wanted
invalid
JokerTV
Mac / OSX
more-info-needed
needs-commercial-sponsor
needs-commercial-sponsor
needs-commercial-sponsor
needs-confirmation-of-being-broken
OCR
pull-request
Mirrored from GitHub Pull Request
 Python
regression
Rust
teletext
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ccextractor#897
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?