mltframework / mltframework/mlt
Self-referenced XML handled poorly
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 387
- Avg merge
- 17h 28m
- Merged PRs (30d)
- 8
Description
At one point I accidentally added the current file to itself while using kdenlive. This resulted in an unopenable file — trying to open it would result in unresponsiveness and gradually increasing RAM usage until the OOM killer stepped in. MLT should probably prevent this sort of self-reference or handle it gracefully (if there's a way to do so?)
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
Start by reproducing the self-referenced XML case described with Kdenlive and MLT, observing whether opening the file hangs or exhausts memory. Trace the XML-loading entry point and determine whether the intended result is to reject self-reference or handle it without becoming unresponsive; done means the file no longer causes the reported failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100