movit library crash when used in kdenlive
When enabling libmovit in kdenlive settings, it always crashes with [code]GL error 0x502 (GL_INVALID_OPERATION)[/code]. Git log from Movit authors: [url]https://git.sesse.net/?p=movit;a=commit;h=2d8043bb837b45c9ae509450b3e1b1eb545e44b9[/url] Unfortunately the change only delays crash from happening, and doesn't prevent it.
When enabling libmovit in kdenlive settings, it always crashes with
GL error 0x502 (GL_INVALID_OPERATION)
.
Git log from Movit authors: https://git.sesse.net/?p=movit;a=commit;h=2d8043bb837b45c9ae509450b3e1b1eb545e44b9
Unfortunately the change only delays crash from happening, and doesn't prevent it.

#1
Posted 07/24/2017 07:45 PM   
That GL error by itself isn't very helpful. You need to know what OpenGL call it was trying to make and what its parameters were. However, from the linked commit, it sounds like there's actually a crash later. Do you know if there's a standalone test app that can demonstrate the crash problem?
That GL error by itself isn't very helpful. You need to know what OpenGL call it was trying to make and what its parameters were. However, from the linked commit, it sounds like there's actually a crash later.

Do you know if there's a standalone test app that can demonstrate the crash problem?

Aaron Plattner
NVIDIA Linux Graphics

#2
Posted 07/24/2017 09:09 PM   
No, I'm sorry but I don't know of any, however an appimage of kdenlive (download here: [url]http://files.kde.org/kdenlive/release/Kdenlive-17.04.1b-x86_64.AppImage[/url]) should work. Appimages are standalone sandboxed executables, add execute permissions and launch it like a regular executable. After startup, go to Settings -> Configure Kdenlive -> Playback and make sure "Use GPU processing (Movit library)" is checked. Add a clip to timeline, anything works. After attempting to start playback the application should crash.
No, I'm sorry but I don't know of any, however an appimage of kdenlive (download here: http://files.kde.org/kdenlive/release/Kdenlive-17.04.1b-x86_64.AppImage) should work. Appimages are standalone sandboxed executables, add execute permissions and launch it like a regular executable. After startup, go to Settings -> Configure Kdenlive -> Playback and make sure "Use GPU processing (Movit library)" is checked. Add a clip to timeline, anything works. After attempting to start playback the application should crash.

#3
Posted 07/24/2017 09:48 PM   
Okay, new info. I launched kdenlive in gdb and it's much more stable. I tried to crash it, but it works just fine.
Okay, new info. I launched kdenlive in gdb and it's much more stable. I tried to crash it, but it works just fine.

#4
Posted 07/25/2017 09:39 AM   
Thanks. Can you please run nvidia-bug-report.sh and attach the nvidia-bug-report.log.gz file to your post?
Thanks. Can you please run nvidia-bug-report.sh and attach the nvidia-bug-report.log.gz file to your post?

Aaron Plattner
NVIDIA Linux Graphics

#5
Posted 07/25/2017 03:34 PM   
personnaly , i think kde should be a part of Mac OS ...not on linux
personnaly , i think kde should be a part of Mac OS ...not on linux

#6
Posted 07/25/2017 04:00 PM   
Attached file as requested to the first post. @Mounir Please refrain yourself from posting those opinions on bug reports, as they have nothing to do with issue at hand.
Attached file as requested to the first post.
@Mounir Please refrain yourself from posting those opinions on bug reports, as they have nothing to do with issue at hand.

#7
Posted 07/25/2017 04:08 PM   
Thanks kiroma, I can reproduce a kdenlive crash, but it's failing an assertion: [code]kdenlive: resource_pool.cpp:578: GLuint movit::ResourcePool::create_vec2_vao(const std::set<int>&, GLuint): Assertion `vao_formats.count(key) == 0' failed.[/code] As far as I can tell from the code, this just means that it corrupted its own internal tracking list of VAOs. If you're in touch with the Movit authors, can you please have them send a more detailed description of the circumstances leading up to the crash and why they believe it is a driver bug to linux-bugs@nvidia.com?
Thanks kiroma,

I can reproduce a kdenlive crash, but it's failing an assertion:
kdenlive: resource_pool.cpp:578: GLuint movit::ResourcePool::create_vec2_vao(const std::set<int>&, GLuint): Assertion `vao_formats.count(key) == 0' failed.

As far as I can tell from the code, this just means that it corrupted its own internal tracking list of VAOs.

If you're in touch with the Movit authors, can you please have them send a more detailed description of the circumstances leading up to the crash and why they believe it is a driver bug to linux-bugs@nvidia.com?

Aaron Plattner
NVIDIA Linux Graphics

#8
Posted 07/26/2017 12:06 AM   
No, I don't have any direct contact with them. I can send a mail to the author of the commits, if that helps. The feature works without any problems on Nouveau drivers, and Intel's iGPU, therefore so far my suspicions landed on the drivers. I have some problems with the AppImage though, it might not be as reliable as I thought at first. P.s. I'm not sure if it's related, but I managed to crash the app under GDB, and got the following: [code]Thread 41 "Thread (pooled)" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fff577fe700 (LWP 10431)] 0x00007fffe9f0d989 in glDeleteTextures () from /usr/lib/nvidia-384/libGL.so.1 [/code]
No, I don't have any direct contact with them. I can send a mail to the author of the commits, if that helps.
The feature works without any problems on Nouveau drivers, and Intel's iGPU, therefore so far my suspicions landed on the drivers.
I have some problems with the AppImage though, it might not be as reliable as I thought at first.

P.s. I'm not sure if it's related, but I managed to crash the app under GDB, and got the following:
Thread 41 "Thread (pooled)" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff577fe700 (LWP 10431)]
0x00007fffe9f0d989 in glDeleteTextures () from /usr/lib/nvidia-384/libGL.so.1

#9
Posted 07/26/2017 09:32 AM   
kiroma did you try this Version 17.03.70 ?
kiroma
did you try this Version 17.03.70 ?

#10
Posted 07/26/2017 11:26 AM   
Version of what?
Version of what?

#11
Posted 07/26/2017 11:53 AM   
version of kdenlive
version of kdenlive

#12
Posted 07/26/2017 12:05 PM   
I'm compiling kdenlive from source but it's not even the root of the problem in this thread. Main problem is with mlt compiled with movit.
I'm compiling kdenlive from source but it's not even the root of the problem in this thread.
Main problem is with mlt compiled with movit.

#13
Posted 07/26/2017 07:12 PM   
Alright, it crashed again with the same output. I might be on to something. I need to compile entire thing with debugging symbols. Oh god. Okay I got the exact same message as aplattner.
Alright, it crashed again with the same output. I might be on to something.
I need to compile entire thing with debugging symbols.
Oh god.

Okay I got the exact same message as aplattner.

#14
Posted 07/29/2017 07:53 PM   
Hello, I have also experienced a similar fate with the nvidia propritetary drivers----The same as kiroma here. However I have found that If you build kdenlive from source and mlt with movit enabled(building this also from source) as well as movit from source, it helps alleviate alot of the problem. If you also go into you settings and switch all the "MJPEG" and all the "MPEG" options in KDENLIVE to X264 that helps as well. If you also set a higher number of proxy threads, mlt threads(experimental), and going into project defaults and enabling proxy clips and setting the first video setting to 250pixels as well as the second images to 1000 pixels, and the encoding profile to X264 that also helps alleviate the problem as well.. Try also messing with the timeline preview setting as well..In the playback tab I have found that setting the audio backend to SDL and the audio driver to ALSA or PulseAudio. I havent gotten it fully to work but I have gotten it to work alot more stablly then it was working before... Just paste this into a file then save to desktop. Open the file from desktop and it should load the settings. Working Settings for me in the forum on configuration file: [url]https://hastebin.com/obagopotis.makefile[/url]
Hello, I have also experienced a similar fate with the nvidia propritetary drivers----The same as kiroma here. However I have found that If you build kdenlive from source and mlt with movit enabled(building this also from source) as well as movit from source, it helps alleviate alot of the problem. If you also go into you settings and switch all the "MJPEG" and all the "MPEG" options in KDENLIVE to X264 that helps as well. If you also set a higher number of proxy threads, mlt threads(experimental), and going into project defaults and enabling proxy clips and setting the first video setting to 250pixels as well as the second images to 1000 pixels, and the encoding profile to X264 that also helps alleviate the problem as well.. Try also messing with the timeline preview setting as well..In the playback tab I have found that setting the audio backend to SDL and the audio driver to ALSA or PulseAudio.

I havent gotten it fully to work but I have gotten it to work alot more stablly then it was working before...

Just paste this into a file then save to desktop. Open the file from desktop and it should load the settings.
Working Settings for me in the forum on configuration file:
https://hastebin.com/obagopotis.makefile

#15
Posted 07/30/2017 01:41 AM   
Scroll To Top

Add Reply