Rendering a video crashes at the end every time

Hi, I have a problem with Kdenlive for quite some time now when it crashes rendering at the end of every try. It leaves this error:

[mp4 @ 0000021561d82b40] 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 @ 0000021561d82b40] Encoder did not produce proper pts, making some up. Current Frame: 124, percentage: 99

The file is still usable but this error just seems wrong and looks like it could corrupt my file one day.

Using MP4-H264/AAC option to render with following arguments

ab=160k acodec=aac channels=2 crf=23 f=mp4 g=15 movflags=+faststart preset=veryfast real_time=-1 threads=0 vcodec=libx264

Kdenlive version: 23.08.3
OS version: Windows 11 Home 23H2 build 22635.2915

Edit:
Log file contents:

Started render process: C:/Program Files/kdenlive/bin/melt.exe -progress C:/Users/Syhma/AppData/Local/Temp/kdenlive-gAkhwj-1.mlt
1	3	2
2	16	12
3	99	79
[mp4 @ 0000021561d82b40] 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 @ 0000021561d82b40] Encoder did not produce proper pts, making some up. Current Frame: 124, percentage: 99Rendering of C:/Users/Syhma/Videos/untitled.mp4 aborted, resulting video will probably be corrupted.
Frame: 99

It seems Frame: 124 has some issues. Divide 124 by the frame rate the project has and you get the second on the timeline on which the problem occur. Maybe there is an effect hindering for proper rendering.

No, I just put the short clip into timeline and hit render. It does not matter what clip and what duration. It always gives the same error for the last frame. No added effects, no nothing. Just just a plain clip on the timeline. I can even get a jpeg on the timeline for 5 sec and render it. It will give me the same error on the last frame.

Is Parallel Processing on? Check the More Options in the render dialog window

Same thing just happened to me. kdenlive 24.12.3 on openSUSE Tumbleweed.

Did you ever figure out what causes this?

Please open a bug report on bugs.kde.org