Bug 374776 - Kdenlive crashes when importing videos after changing their location
Summary: Kdenlive crashes when importing videos after changing their location
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kdenlive
Classification: Applications
Component: Rendering & Export (show other bugs)
Version: 16.12.0
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-08 20:02 UTC by aljullu
Modified: 2017-02-06 16:47 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
backtrace (19.26 KB, text/plain)
2017-01-08 20:02 UTC, aljullu
Details
Project file (220.92 KB, text/xml)
2017-01-20 23:06 UTC, aljullu
Details

Note You need to log in before you can comment on or make changes to this bug.
Description aljullu 2017-01-08 20:02:59 UTC
Created attachment 103293 [details]
backtrace

Application: kdenlive (16.12.0)

Qt Version: 5.7.1
Frameworks Version: 5.29.0
Operating System: Linux 4.8.15-300.fc25.x86_64 x86_64
Distribution: "Fedora release 25 (Twenty Five)"

-- Information about the crash:
- What I did before:
I created a Kdenlive project (v. 16.04 or 16.08, IIRC) with Fedora 24 Workstation on Gnome. It was using some video files from a partition that I mounted every time I wanted to work on the project (sudo mount /dev/sda1 /mnt).

Yesterday I made a fresh install of Fedora 25 Workstation (I installed both, KDE and Gnome, but I kept using Gnome). Today I was reordering some of my files in the partition.

- What I was doing when the application crashed:
When opening the project again, it asked me to provide the new location of the files, I chose the new folder and then it crashed.

- Related issue?
Few minutes before it worked ok (it could get the files from the new location correctly), but was constantly crashing when clicking on a title clip in the library panel. The output on the console was this one:
QXcbConnection: XCB error: 8 (BadMatch), sequence: 39197, resource id: 50332215, major code: 130 (Unknown), minor code: 3

Not sure if these two issues are related.
Comment 1 Christoph Feck 2017-01-09 22:32:06 UTC
A valgrind log would be nice. Also, if possible, please attach the project file (xml file) you see this crash with.

Relevant part of backtrace from comment #0:

Thread 7 (Thread 0x7fe1334ea700 (LWP 12175)):
[KCrash Handler]
#6  0x00007fe198d8491f in raise () at /lib64/libc.so.6
#7  0x00007fe198d8651a in abort () at /lib64/libc.so.6
#8  0x00007fe198dc8200 in __libc_message () at /lib64/libc.so.6
#9  0x00007fe198dd188a in _int_free () at /lib64/libc.so.6
#10 0x00007fe198dd52bc in free () at /lib64/libc.so.6
#11 0x00007fe15ce9e5db in on_start_element () at /usr/lib64/mlt/libmltxml.so
#12 0x00007fe195645dde in xmlParseStartTag () at /lib64/libxml2.so.2
#13 0x00007fe195651758 in xmlParseElement () at /lib64/libxml2.so.2
#14 0x00007fe195650bdf in xmlParseContent () at /lib64/libxml2.so.2
#15 0x00007fe1956515c3 in xmlParseElement () at /lib64/libxml2.so.2
#16 0x00007fe195651ccb in xmlParseDocument () at /lib64/libxml2.so.2
#17 0x00007fe15ce9f6c0 in producer_xml_init () at /usr/lib64/mlt/libmltxml.so
#18 0x00007fe1a1fe044a in mlt_factory_producer () at /lib64/libmlt.so.6
#19 0x00007fe1a1db0f66 in Mlt::Producer::Producer(Mlt::Profile&, char const*, char const*) () at /lib64/libmlt++.so.3
#20 0x000055f6cff21e2f in Clip::clone() ()
#21 0x000055f6d01e4458 in ProjectClip::thumbProducer() ()
#22 0x000055f6d01e569c in ProjectClip::doExtractImage() ()
Comment 2 aljullu 2017-01-20 23:06:48 UTC
Created attachment 103567 [details]
Project file

Here is the XML project file. I don't know exactly how to generate the valgrind log. However, I couldn't reproduce this error any more.
Comment 3 farid 2017-02-05 20:18:13 UTC
So can we close this issue?
Comment 4 aljullu 2017-02-06 09:26:20 UTC
I couldn't reproduce this error any more, so yes, you can close it. Just wanted to upload the backtrace in case it was useful for you.
Comment 5 farid 2017-02-06 16:47:37 UTC
(In reply to aljullu from comment #4)
> I couldn't reproduce this error any more, so yes, you can close it. Just
> wanted to upload the backtrace in case it was useful for you.

Thanks for your help, the thing is if we cannot reproduce it the devs can't fix it. If it ever happens again please let us know. Cheers :D