-
Notifications
You must be signed in to change notification settings - Fork 322
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Melt crashes at the end of the rendering #786
Comments
Thanks for the report. Unfortunately, those two log messages are only information and do not provide a hint about what caused the crash. Were there any other messages? Can you recreate the crash, or was this a one-time occurance? |
The crash happens when I rendered a 1080p 60fps video as H.264 codec using Kdenlive, I then wait the rendering to finish, and when it reaches 99%, the renderer crashes. It had happened once and when I tried again, it happened again. System specifications: |
P.S. Kdenlive is quite buggy, I installed it, and the first time running it it has a black GUI, then I uninstalled and tried older versions, they work fine, until I change the renderer to DirectX, then I updated my PC and restarted, the issue was fixed. I tried rendering a video as well, using the lowest quality by sliding the knob to the very left is successful in rendering, but when I used default settings, it crashed like I reported. P.P.S. the library that caused melt to crash is libmlt-7.dll as reported by Windows. |
It seems to me that libmlt-7.dll is very problematic and causes every crash, is there a fix? I have to release my new video soon. A reinstallation did not fix. |
Sometimes there is a crash at the end when it tries to close and cleanup, but cleanup is not necessary because the operating system kernel takes care of things. Still it can be difficult to prevent cleanups because running code needs them. The point is: check the output file to see if it is ok. Otherwise, no, there is no fix because we do not reproduce your problem: only you and you have not fixed it. |
I will be sure to check it out. But downgrading Kdenlive to older versions (like this one) clears the problem out of the way. |
@ddennedy we also experience this on Linux. We tried with v7.4, v7.6 or v7.8 and it's all the same. I confirm it's just at the end as the output file is generated and OK. We cannot provide more information as the only thing we see is a segfault but we can say that the more concurrent melt process you have running on the machine the more likely to see the segfault. |
Maybe you could try prefixing melt command with "catchsegv" utility to get a stack trace and help debugging which service, which function fails. You must have debug symbols to provide more informative output (do you build from source or use packages ? In the latter case, which distro?) |
Does your video have any effects or anything else? Does it happen with just a clip? What kind of footage are you using? Can you provide a small sample so I can try to reproduce? |
We are using a lot of effects yes but they differ and those crashes are random in more than 20 different melt files. We build from source from https://github.com/mltframework/mlt-scripts/blob/master/build/build-melt.sh What should we change in this script to get the debug symbols? We can easily run it with catchsegv after for you. |
I'd try first to add "-DCMAKE_BUILD_TYPE=RelWithDebSymbols" to mlt options |
Here is the error we have with the kdenlive file we used.
|
@vpinon anything more we can do to help on this? Still happening a lot on our side. |
Sorry, I'm not much involved in MLT & Kdenlive development for some time. |
@Webonaute repeatedly you are warned about an X11 environment for Qt, but it seems you are ignoring that. You can try to add the undocumented |
Here's the log:
Rendering of X:/My Drive/Videos/HometoPnP Highspeed-6000.mp4 crashed
[mp4 @ 000000000222d2c0] 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 @ 000000000222d2c0] Encoder did not produce proper pts, making some up. [mp4 @ 000000000222d2c0] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 12192768 >= 12192768
The text was updated successfully, but these errors were encountered: