Bug 479979

Summary: Automatic Scene Split has 50% chance freezing whole GUI
Product: [Applications] kdenlive Reporter: red_Arti <jijiliu35>
Component: User Interface & MiscellaneousAssignee: 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
SUMMARY
If use Automatic Scene Split on a video > 3min, there's 50% chance of freezing the whole GUI.


STEPS TO REPRODUCE
1. Create project and add a video about 3~5 minutes
2. Right-click video in bin -> Clip jobs -> Automatic Scene Split
3. Set threshold = 10 . Click OK

OBSERVED RESULT
GUI freeze happends often

EXPECTED RESULT

SOFTWARE/OS VERSIONS
Reproduced on:
1. Kdenlive 24.04.70 AppImage git ci built. KDE 5.246.0, Qt 6.6.0
2. Kdenlive 23.08.4 Flatpak, KDE Frameworks Version 5.113.0, Qt Version 5.15.10 (built against 5.15.10) 


My system:
KDE Plasma Version: 5.27.9
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Graphics Platform: X11
Memory: 12 GiB of RAM

ADDITIONAL INFORMATION
Comment 1 Jean-Baptiste Mardelle 2024-01-19 14:19:42 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 ) ?
Comment 2 red_Arti 2024-01-20 12:34:42 UTC
(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.
Comment 3 red_Arti 2024-01-20 13:41:06 UTC
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.