mltframework / mltframework/mlt
About the release of memory after the closed project
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 387
- Avg merge
- 17h 28m
- Merged PRs (30d)
- 8
Description
When I first opened shutcut, the memory was at 110MB.
After I create a projuect. Now memory is 544MB
the project like
Finally, I close the project. Memory has been around 544MB
So, my question is:Mlt memory is not released after closing the project?
Repeat to create a project, close the project, the memory will continue to rise until the shutcut program crashes。I think this is the problem mlt, I would like to know if this is a bug or itself is such。
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Reproduce the issue by creating and closing projects repeatedly while monitoring process memory, then trace the project-close lifecycle to identify whether memory grows without returning toward its baseline. Done means repeated cycles no longer cause unbounded growth.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100