| Summary: | Keeps randomly crashing (segfault) by just using it every couple of minutes | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | roland |
| Component: | User Interface & Miscellaneous | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED WAITINGFORINFO | ||
| Severity: | grave | CC: | wegwerf-1-2-3 |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
roland
2016-06-04 18:01:11 UTC
Roland, which version of Kdenlive, MLT, and ffmpeg/avconf do you use? Where did you get them from? Distribution repository, Kdenlive project repository, or self-compiled? I'm afraid that with the terse information given, the backtrace won't be of much use, more so as the crash is probably randomly in the pthread_cond_wait. The crash is of generic nature. I've replicated it also on a out-of-the box installation of Kubuntu 16.04 LTS 64-Bit. Just install KDEnlive right after installing the Distro and it segfaults straight away. The stack trace though is from my GenToo system. So it's self-compiled. Here the information which might help. The crashes happen both with 15.12.3 and 16.04.1 and both on GenToo and Kubuntu. KDEnlive ( https://gitweb.gentoo.org/repo/gentoo.git/tree/kde-apps/kdenlive ): kdenlive-15.12.3 MLT ( https://gitweb.gentoo.org/repo/gentoo.git/tree/media-libs/mlt ): media-libs/mlt-0.9.8-r2 FFMpeg ( https://gitweb.gentoo.org/repo/gentoo.git/tree/media-video/ffmpeg ): media-video/ffmpeg-2.8.6 USE flags (defines what is compiled in. usually maps rather directly to configure options, - prefixed means disabled). media-libs/mlt-0.9.8-r2::gentoo USE="ffmpeg frei0r gtk jack kdenlive libsamplerate lua melt opengl python qt5 sdl xml -compressed-lumas -debug -fftw -kde -libav -qt4 -rtaudio (-ruby) -vdpau -xine" CPU_FLAGS_X86="mmx sse sse2" PYTHON_TARGETS="python2_7" media-video/ffmpeg-2.8.6:0/54.56.56::gentoo USE="X aac alsa bzip2 encode fontconfig frei0r gpl hardcoded-tables iconv jack ladspa modplug mp3 network openal opengl postproc samba sdl theora threads truetype vorbis vpx x264 xcb xvid zlib -aacplus (-altivec) -amr -amrenc (-armv5te) (-armv6) (-armv6t2) (-armvfp) -bluray -bs2b -cdio -celt -cpudetection -debug -doc -examples -faac -fdk -flite -fribidi -gme -gnutls -gsm -iec61883 -ieee1394 -jpeg2k -libass -libcaca (-libressl) -librtmp -libsoxr -libv4l -lzma (-mipsdspr1) (-mipsdspr2) (-mipsfpu) (-neon) -openssl -opus -oss -pic -pulseaudio -quvi -schroedinger -snappy -speex -ssh -static-libs {-test} -twolame -v4l -vaapi -vdpau -wavpack -webp -x265 -zvbi" ABI_X86="(64) -32 (-x32)" CPU_FLAGS_X86="avx fma3 fma4 mmx mmxext sse sse2 sse3 sse4_1 sse4_2 ssse3 xop -3dnow -3dnowext -avx2" FFTOOLS="aviocat cws2fws ffescape ffeval ffhash fourcc2pixfmt graph2dot ismindex pktdumper qt-faststart sidxindex trasher" If you need more I can try adding the information. Roland, a few things I notice: 1. MLT is outdated, you should upgrade to MLT 6.0.x or 6.2.x if possible. The version gap looks larger than it actually is, but there have been some important bug fixes in MLT with respect to Kdenlive. So if possible, please upgrade MLT. 2. 15.12.3 isn't supported anymore, but you mentioned 16.04.1, so this is recent. 3. The stack trace doesn't seem to make much sense to me at the moment, I'll try to explain why. What is curious is that you may see a crash in pthread_cond_wait() ... is this actually the thread that crashed or is this just the stack trace of one of the multiple Kdenlive threads? What crash did you actually see, a segmentation fault, bus error, or ... ? I've seen "crashes" mostly in pthread_cond_wait() when the crash actually was in a different thread. Of course, I may be on the wrong track here, so that's why I'm asking. In case you didn't already do it this way: can you please run gdb src/kdenlive from your kdenlive build folder. When kdenlive crashes, is the "bt" command giving the same back trace? 1) MLT >= 6.0 is masked "testing" in GenToo which is usually for a reason. But Kubuntu has 6.0.0-2 and there it segfaults too so that should not be the reason. 3) Unfortunatly I can't. When I run it with GDB and it crashed KCrash steals the process from GDB and I end up with no stack trace. I see though some strange entries in the GDB before it crashes: QXcbConnection: XCB error: 8 (BadMatch), sequence: 30604, resource id: 67109068, major code: 131 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 30620, resource id: 67109068, major code: 131 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 30637, resource id: 67109068, major code: 131 (Unknown), minor code: 3 QXcbConnection: XCB error: 8 (BadMatch), sequence: 30656, resource id: 67109068, major code: 131 (Unknown), minor code: 3 ( a lot of these actually) and some of these: Attempting to create QWindow-based QOffscreenSurface outside the gui thread. Expect failures. or this one: Overwriting existing old cached entry due to collision. Overwriting existing old cached entry due to collision. Not sure how to get around KCrash when using GDB Roland, thank you for your information. 1) Agreed. However, there is no reason for masking MLT 6.0.x as this is a rock solid release. And it has the ugly titler crash finally fixed. But, as you said, that's of no concern for the moment. 2) The XCB errors usually can be ignored, they are seen on many systems and seem to stem from Qt. When you run your self-compiled Kdenlive (from build/src) under gdb control then KCrash should not interfere. This is what I experience on my Kubuntu 16.04 installation. What kind of graphics card and drivers do you use? Kdenlive requires OpenGL. Did you disable movit, the GPU acceleration support in Kdenlive? In case you should have it enabled, can you please disable it? Also, can you please make sure that you've set processing threads set to 1 in Kdenlive's configure dialog? And what is also strange: I'm on a Kubuntu 16.04 stock installation, but have compiled my own Kdenlive from (bleeding) git master, as well as MLT, and ffmpeg. This has proven to be a solid combination independent of any distro woes. The stock components are Qt5 and KF5, as well as X11 and the graphics card driver -- which is the open source AMD Radeon driver with an HD 7700/7800. But unfortunately, you are seeing a lot of crashes on your system. So this brings me to the last question I can ask: what kind of system do you have? Did you experience any other odd system behavior that may hint at a faulty RAM bank or similar? Does other graphics-heavy software, such as Blender, Natron, GIMP with large images, work correctly? If yes, this then can probably safely wipe out RAM woes. To be honest, I'm dazzled... GPU is a Radeon HD 7970 with Catalyst ( https://packages.gentoo.org/packages/x11-drivers/ati-drivers ). Processing threads is already set to 1. What about concurrent threads? Looking at the USE flags I would say OpenGL is already disabled: kde-apps/kdenlive-15.12.3:5::gentoo USE="handbook -debug -gles2 -v4l" Where is "moveit"? I can not find it in the configuration dialog. Otherwise the RAM is certainly not the problem. I'm doing game-deving so the machine is regularly stressed GPU/RAM wise. OpenGL must be *enabled*, as Kdenlive relies on it for display. Movit is the experimental GPU accel support, it's fine to have it off -- it's something about use GPU acceleration or the like; I was just asking to ensure that this is not caused by movit. Concurrent threads can (and should) be set to a higher value, depending on your system. Only processing threads=1 is important for now as otherwise the timeline playhead won't respond correctly. Also just to be on the safe side here. |