mltframework / mltframework/shotcut
closing a project does not release all memory
Open
Nobody has claimed this yet.
reproduced by dev
- Dominant language
- C++
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 11h 27m
- Merged PRs (30d)
- 5
Description
After analysis, I found that the shotcut will not release the memory when it closes the project, and I think this is the reason for MLT. Is there any way to solve it?I tried to modify the structure of the code, but I found that many variables were static local variables that could not be released.I'm troubled.
Contributor guide
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 file, test, or entry point is named. Start by tracing project-closing cleanup and measuring memory before and after closing a project; done means confirming that project resources are released without regressing normal project behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100