Bug 375859

Summary: Loading project created in 0.9.10 results in "double free or corruption (fasttop)"
Product: [Applications] kdenlive Reporter: Alan Hagge <nospam.ah>
Component: Rendering & ExportAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED LATER    
Severity: normal CC: wegwerf-1-2-3
Priority: NOR    
Version First Reported In: 16.12.1   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Sample 0.9.10 project file which exhibits the issue.

Description Alan Hagge 2017-02-01 18:08:48 UTC
Created attachment 103753 [details]
Sample 0.9.10 project file which exhibits the issue.

Attempting to load a project created in Kdenlive 0.9.10 crashes during the opening of the project in version 16.12.1 with the following error message:

*** Error in `kdenlive': double free or corruption (fasttop): 0x00007f4b6800cf70 ***

I've attached a sample project (no media, just the project file).  I have the /var/crash/_usr_bin_kdenlive.2000.crash file, but it's 39 MB (gzipped), so I can't attach it here.  If there's an alternate way to get the file to you, let me know.  I've extracted the stack trace from the file and attached it below.

Please let me know what else I can supply to help troubleshoot this issue.

Thanks!
Comment 1 Wegwerf 2017-02-05 08:50:16 UTC
As explained on Kdenlive website, only current stable release and development branch are supported and maintained. Thank you for your cooperation.
Comment 2 Alan Hagge 2017-02-05 18:03:28 UTC
Hello,

I'd like to respectfully request that this bug report be reopened, as it was in fact filed against the current stable release (16.12.1).  The bug concerns the ability to open a project originally created in a prior version.  I would hope that you would agree that maintaining the ability to open projects from prior versions of kdenlive is an important functionality, as it would render the software much less useful to have to recreate a project from scratch every time kdenlive was upgraded to a new version.

By way of incentive, I've been able to narrow down the part of old project that's causing the crash.  If I remove the XML code for one of the titles, it allows the old project to open successfully (although the other titles in the project are not being displayed properly, but we'll ignore that for now).  Specifically, this is the offending XML code (lines 1177-1205 in the project file attached):

 <producer in="0" out="14999" id="17">
  <property name="length">15000</property>
  <property name="eof">pause</property>
  <property name="resource"/>
  <property name="progressive">1</property>
  <property name="aspect_ratio">1</property>
  <property name="seekable">1</property>
  <property name="mlt_service">kdenlivetitle</property>
  <property name="xmldata">&lt;kdenlivetitle width="1920" duration="450" height="1080" out="450" LC_NUMERIC="en_US.UTF-8">
 &lt;item z-index="1" type="QGraphicsTextItem">
  &lt;position x="485" y="214">
   &lt;transform>1,0,0,0,1,0,0,0,1&lt;/transform>
  &lt;/position>
  &lt;content font-color="255,0,0,255" font-outline-color="0,0,0,255" font-pixel-size="75" font-italic="0" alignment="4" font-underline="0" font-weight="50" font="Impact" font-outline="4">SG Elite 17 Roshambo


SCVA Qualifier #2
01/30/2016
American Sports Center, Anaheim&lt;/content>
 &lt;/item>
 &lt;startviewport rect="0,-1019.91,1920,1080"/>
 &lt;endviewport rect="-0.0128341,978.372,1920,1080"/>
 &lt;background color="0,0,0,0"/>
&lt;/kdenlivetitle>
</property>
  <property name="force_reload">0</property>
  <property name="meta.media.width">1920</property>
  <property name="meta.media.height">1080</property>
 </producer>


If these lines are removed from the project file, the project import and opens successfully.

Thank you for the feedback, and for your willingness to re-examine this report.
Comment 3 Wegwerf 2017-02-05 19:36:16 UTC
I beg your pardon, as I'm clearly at fault here.

Thank you very much for narrowing down the possible cause of the bug. I tested your attached example project file, but unfortunately(?) I don't get a crash with recent Kdenlive git master. I'm getting the usual "Clip Problems" dialog, press "Use placeholders...", and it loads without crashes. Not exactly what we both would like it to do in order to reproduce the crash, I'm afraid.

By the way: are you installing Kdenlive from the Kdenlive ppa's or from stock Ubuntu ppa's?

Because I cannot reproduce, I'm reverting this bug report to "unconfirmed".
Comment 4 Alan Hagge 2017-02-05 19:46:02 UTC
Thank you for your willingness to reopen this report.  I understand that there's not much that can be done unless/until the bug can be reproduced.

As time permits, I'll try to further massage the project file to try to come up with a version that will exhibit the behavior with as little extraneous input (video files, etc.) as possible.  I believe that the issue is with the titles, so I'm going to try to strip out everything but them.  But XML isn't my forte, so trying to manually modify the file is slow going.

To answer your questions - I'm using version 4:16.12.1-2~ubuntu16.10.14:16.12.1-2~ubuntu16.10.1 from the kdenlive-stable yakkety PPA (ie. deb http://ppa.launchpad.net/kdenlive/kdenlive-stable/ubuntu yakkety main) on an Ubuntu MATE 16.10 system.
Comment 5 Jean-Baptiste Mardelle 2017-02-05 19:59:53 UTC
I cannot reproduce either. As Wegwerf said, it would help to know how you installed Kdenlive and which MLT version you have.
Comment 6 Wegwerf 2017-02-05 20:07:15 UTC
Thanks for the information; I just wanted to ensure that you did not got bitten by the stock Ubuntu Kdenlive versions. Stable branch is fine.

I don't think that further stripping down the project will help, especially since this is a corruption issue (don't think it's a double free, because that would probably be reproducible).
Comment 7 Wegwerf 2017-02-05 20:10:43 UTC
The only thing you may try is to check with the AppImage version of Kdenlive. This may help in the sense that you could load the project, but probably doesn't help in finding the cause for the memory space corruption.
Comment 8 Wegwerf 2017-02-05 20:14:51 UTC
BTW, I noticed some lonely transition(s) around 1:50:00 between tracks Video 2 and Video 3, without any clips around them.
Comment 9 Alan Hagge 2017-02-07 00:01:16 UTC
Thank you for your efforts with this issue (you too JBM!).  My further attempts to isolate the issue have proven futile.  I have been able to crash the AppImage version as well, but have not been able to create a reproducible test case.  Even something as simple as moving the project file from one directory to another has in some cases allowed it to be opened successfully.

At this point, I'm willing to chalk it up to some kind of issue with my system.  In every case thus far, I've been able to get the file to open via some other means, such as moving the project file or using the AppImage version instead of the locally-installed one.

Thanks again for your time, and I look forward to continuing to use and enjoy Kdenlive!  Feel free to close this bug report.
Comment 10 Wegwerf 2017-02-08 08:44:30 UTC
Feel free to reopen if necessary!