| Summary: | Automatic Scene Split has 50% chance freezing whole GUI | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | red_Arti <jijiliu35> |
| Component: | User Interface & Miscellaneous | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | snd.noise |
| Priority: | NOR | ||
| Version First Reported In: | git-master | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
red_Arti
2024-01-18 04:18:07 UTC
Thanks for your report. I cannot reproduce, will try later on another computer. Does it freeze while displaying the job progessbar in the bin or at the end of the job (when adding the clip markers ) ? (In reply to Jean-Baptiste Mardelle from comment #1) > Thanks for your report. I cannot reproduce, will try later on another > computer. Does it freeze while displaying the job progessbar in the bin or > at the end of the job (when adding the clip markers ) ? It freezes while displaying the job progessbar. It can randomly happens anytime, at 10%, or at 90% progress. I tried running Kdenlive from terminal and see the logs. Once begin scene detection, Kdenlive starts outputing ffmpeg's progress log to terminal: 1.xxx 4.xxx ..... 120.xxx 126.xxx (stops here) After 2 minutes, Kdenlive GUI freezes and it stops outputing ffmpeg's log. But ffmpeg continues working. Then after another 3 minutes, Kdenlive outputs: GOR RESULTS: (1.xxx 4.xxx ..... 120.xxx 126.xxx....... 340.xxx, 360.xxx ) Kdenlive got the final result, but GUI freezes, and the "outputing ffmpeg's log" thread seemed already died during the process. |