Bug 458252

Summary: Kdenlive Rendering Crash
Product: [Applications] kdenlive Reporter: candide <m8oxu4nv3>
Component: Rendering & ExportAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED WORKSFORME    
Severity: normal CC: snd.noise
Priority: NOR    
Version First Reported In: 22.08.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: export log

Description candide 2022-08-24 13:45:22 UTC
Created attachment 151552 [details]
export log

SUMMARY
***
For the past year, I've been experiencing crashes every time I render a video. The rendered video plays fine, but I'll get a crash report, and the rendering log remains in the folder. This has been the case for a number of export formats.
***


STEPS TO REPRODUCE
1. Edit a clip.
2. Export it in MP4 H264/AAC (see attachment for settings)

OBSERVED RESULT
Rendering will end with crash

EXPECTED RESULT
Rendering ends with no crash

SOFTWARE/OS VERSIONS
Windows: 10


ADDITIONAL INFORMATION
Added log files in attachment

ERROR LOG
Rendering of C:/Users/.../Downloads/vid.mp4 crashed

mlt_repository_init: failed to dlopen C:\Program Files\kdenlive\lib\mlt/libmltjack.dll ("C:\Program Files\kdenlive\lib\mlt\libmltjack.dll": The specified module could not be found.) Current Frame: 1, percentage: 0
[scroll @ 0000021ad989c5c0] [Eval @ 000000d3eb1fe790] Invalid chars ':00:00.000=0' at the end of expression '00:00:00.000=0' [scroll @ 0000021ad989c5c0] Unable to parse option value "00:00:00.000=0" [scroll @ 0000021ad989c5c0] [Eval @ 000000d3eb1fe790] Invalid chars ':00:00.000=0.102871' at the end of expression '00:00:00.000=0.102871' [scroll @ 0000021ad989c5c0] Unable to parse option value "00:00:00.000=0.102871"
[mp4 @ 0000021ad992b880] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly [mp4 @ 0000021ad992b880] Encoder did not produce proper pts, making some up.
Comment 1 farid 2022-08-26 19:20:26 UTC
Are you still experiencing this? If yes, please comment on issue 447854 since it is similar to this one but with more debug information.

*** This bug has been marked as a duplicate of bug 447854 ***
Comment 2 Bug Janitor Service 2022-09-10 04:36:51 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2022-09-25 04:48:56 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!