Summary: | KDenlive rendering instance crashing. | ||
---|---|---|---|
Product: | [Applications] kdenlive | Reporter: | Martin List-Petersen <marlow> |
Component: | Rendering & Export | Assignee: | Jean-Baptiste Mardelle <jb> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | fritzibaby, snd.noise |
Priority: | NOR | Flags: | fritzibaby:
timeline_corruption+
|
Version First Reported In: | 21.12.3 | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Microsoft Windows | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Martin List-Petersen
2022-03-14 21:02:31 UTC
Your log show x265 rendering. Does this happen if you render with x264 as well? Rendered in h264, it also crashes. Now it does actually render the video export without any issues with it. But I get a crash report every single time. Output from the h264 render: Rendering of D:/Users/Marlow/Videos/20220320-Panasonic_GH5-II_and_GH6_power_delivery/Panasonic_GH5-II_and_GH6_power_delivery_h264.mp4 crashed [mp3float @ 0000000002bcce00] Could not update timestamps for skipped samples. Current Frame: 4, percentage: 0 [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff0a1040] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff0a1040] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000fefd84c0] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000fefd84c0] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff3aa740] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff3aa740] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000feec6d80] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000feec6d80] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000fef82f40] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000fef82f40] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000014d0e380] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000014d0e380] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000014d0dd00] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000014d0dd00] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff468c00] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff468c00] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff46ab80] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff46ab80] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff467f40] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff467f40] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000014d0b740] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 0000000014d0b740] overread end of atom '[169]swr' by 3 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff98ab40] overread end of atom '[169]mak' by 2 bytes [mov,mp4,m4a,3gp,3g2,mj2 @ 00000000ff98ab40] overread end of atom '[169]swr' by 3 bytes [mp3float @ 0000000002bcce00] Could not update timestamps for discarded samples. Current Frame: 20437, percentage: 99 [mp3float @ 0000000002bcce00] Could not update timestamps for discarded samples. [mp4 @ 0000000002c4f240] 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 @ 0000000002c4f240] Encoder did not produce proper pts, making some up. [mp4 @ 0000000002c4f240] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 32733184 >= 32733184 [mp3float @ 0000000002bcce00] Could not update timestamps for discarded samples. [mp3float @ 0000000002bcce00] Could not update timestamps for discarded samples. [mp3float @ 0000000002bcce00] Could not update timestamps for discarded samples. 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 *** |