Hi everybody !

I have a serious problem with my Kdenlive Version 0.7.3 Using KDE 4.2.2 (KDE 4.2.2) on my Ubuntu 9.04
(Kdenlive is taken from Kdenlive repository).

I create a large project of something like 450 videos and, after Kdenlive crashed while I was editing my project,
it cannot be loaded again into Kdenlive. I'm in a desperate situation, I cannot continue developing my
project and all my work may be lost.

I fixed broken projects several times before by manually removing bad producers from my project,
but now I canot even fugure out which of my 450 videos causes the problem.

Is it possible to get some additional diagnostics at least to try to find out what is wrong ?

I'll maybe set all up and build Kdenlive from sources, but this will take long, as kdenlive is
not that simple software.

I think there is no reason to post this as a bug, as they will not be able to reproduce it,
as the project is huge.

I whould be glad for any help.

Thank you.

This is the backtrace:
----------------------
Application: Kdenlive (kdenlive), signal SIGSEGV
[Current thread is 0 (LWP 16604)]

Thread 3 (Thread 0xb242eb90 (LWP 16623)):
#0 0xb8047430 in __kernel_vsyscall ()
#1 0xb661d412 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2 0xb6724344 in __pthread_cond_timedwait (cond=0x9b024e0, mutex=0x9b024c8, abstime=0xb242e188) at forward.c:152
#3 0xb8021a09 in mlt_consumer_get_frame () from /usr/lib/libmlt.so.1
#4 0xb661a9ce in __pthread_mutex_lock (mutex=0xb065de00) at pthread_mutex_lock.c:43
#5 0x00000002 in ?? ()

Thread 2 (Thread 0xb1c2db90 (LWP 16624)):
#0 0xb8047430 in __kernel_vsyscall ()
#1 0xb661d0e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb67242ed in __pthread_cond_wait (cond=0x9af37ac, mutex=0x9af37dc) at forward.c:139
#3 0xb46ebd2c in ?? () from /usr/lib/mlt/libmltsdl.so
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Thread 1 (Thread 0xb5de7700 (LWP 16604)):
[KCrash Handler]
#6 0x0813b77e in KdenliveDoc::isTrackLocked ()
#7 0x081762ca in TrackView::parseDocument ()
#8 0x08177955 in TrackView::TrackView ()
#9 0x080d6137 in MainWindow::doOpenFile ()
#10 0x080d80a1 in MainWindow::openFile ()
#11 0x080e9555 in MainWindow::qt_metacall ()
#12 0xb7408ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb7409932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb7cf9fb3 in KRecentFilesAction::urlSelected () from /usr/lib/libkdeui.so.5
#15 0xb7cfa37d in ?? () from /usr/lib/libkdeui.so.5
#16 0xb7cfa4f3 in KRecentFilesAction::qt_metacall () from /usr/lib/libkdeui.so.5
#17 0xb7408ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb7409932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb7cfdd23 in KSelectAction::triggered () from /usr/lib/libkdeui.so.5
#20 0xb7cff740 in KSelectAction::actionTriggered () from /usr/lib/libkdeui.so.5
#21 0xb7d00a14 in KSelectAction::qt_metacall () from /usr/lib/libkdeui.so.5
#22 0xb7cfa43a in KRecentFilesAction::qt_metacall () from /usr/lib/libkdeui.so.5
#23 0xb7408ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#24 0xb7409932 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#25 0xb69f85d3 in QActionGroup::triggered () from /usr/lib/libQtGui.so.4
#26 0xb69f8e58 in ?? () from /usr/lib/libQtGui.so.4
#27 0xb69f906e in QActionGroup::qt_metacall () from /usr/lib/libQtGui.so.4
#28 0xb7408ca8 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#29 0xb74090e0 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#30 0xb69f3891 in QAction::triggered () from /usr/lib/libQtGui.so.4
#31 0xb69f4e0f in QAction::activate () from /usr/lib/libQtGui.so.4
#32 0xb6e6f01c in ?? () from /usr/lib/libQtGui.so.4
#33 0xb6e7576b in ?? () from /usr/lib/libQtGui.so.4
#34 0xb6e76242 in QMenu::mouseReleaseEvent () from /usr/lib/libQtGui.so.4
#35 0xb7ebc7e5 in KMenu::mouseReleaseEvent () from /usr/lib/libkdeui.so.5
#36 0xb6a50b43 in QWidget::event () from /usr/lib/libQtGui.so.4
#37 0xb6e78629 in QMenu::event () from /usr/lib/libQtGui.so.4
#38 0xb69f9e9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#39 0xb6a02b11 in QApplication::notify () from /usr/lib/libQtGui.so.4
#40 0xb7dd594d in KApplication::notify () from /usr/lib/libkdeui.so.5
#41 0xb73f2a3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#42 0xb6a01b7e in QApplicationPrivate::sendMouseEvent () from /usr/lib/libQtGui.so.4
#43 0xb6a71c06 in ?? () from /usr/lib/libQtGui.so.4
#44 0xb6a70ca7 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#45 0xb6a9bc6a in ?? () from /usr/lib/libQtGui.so.4
#46 0xb614db88 in IA__g_main_context_dispatch (context=0x97df108) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:1814
#47 0xb61510eb in g_main_context_iterate (context=0x97df108, block=1, dispatch=1, self=0x97dd620) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2448
#48 0xb6151268 in IA__g_main_context_iteration (context=0x97df108, may_block=1) at /build/buildd/glib2.0-2.20.1/glib/gmain.c:2511
#49 0xb741e438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#50 0xb6a9b365 in ?? () from /usr/lib/libQtGui.so.4
#51 0xb73f106a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#52 0xb73f14aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#53 0xb73f3959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#54 0xb69f9d17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#55 0x080ca8cc in main ()

My problem has been solved, the case may be closed.

It seems there was a problem with disk. After automatic re-indexing or whatever of the disk
afer next reboot the project is read. Nethetheless, I'm still interested in some way of understanding in details what Kdenlive does during project loading. Is there some log or jornal ?

I'm sorry for my previous post, I just was so happy seeing my project again in Kdenlive ...

Actually, what happens is Kdenlive occasionally loads my project, but this happens rare.

So the problem still exists.

I'va re-installed Kdenlive from the Ubuntu repository and my project opened once, then the situation
repeated.

I think I have to build Kdenlive from the latest sources.

I'll try to inform of the problem.

Is it possible to split a project to two peaces ?
By hand or with help of some tool ?

Is there a DTD/Schema form KDENLive projects ?

There is a DTD for the MLT part of the XML, it is named mlt-xml.dtd. However, kdenlive adds elements and does not use namespaces. In any case, I do not think the DTD will help much. You can carefully edit the project file in a text editor and then check that is is well-formed XML using xmllint at the command line.

Since the last MLT release, I fixed some race conditions in the SDL plugin. In particular, I discovered them while suffering crashes when loading a project file in Kdenlive. This coincided with my switch from a dual core to a quad core system. It seems the increase parallelism aggravated the race conditions. However, I can not say from your backtrace that you are hitting the same problem. Your segfault is occurring somewhere in kdenlive/kde/qt.

Thank you for responce.

I also suspect some races, as sometimes (!) it loads (but very rare).

Maybe I should try limiting KdenLive to only one CPU (I have a dual-cored PC).

And what about DTD - I wanted to split my project to two or more parts.
DTD could have helped.

I have managed to fix this in my project by building from the latest sources from the SVN repository and debugging.

The problem was in my project XML data, in one of my transitions.

I had

<![CDATA[
4
5
fezzik
transition
luma
1
0
0
0



5
6
fezzik

transition
luma
1
0
1
0
1

]]>

In "transition36" b_track was 6, which referenced to a wrong track, I had only 5 tracks.

As a workaround, I changed


<![CDATA[
5
6
]]>

to

<![CDATA[
5
4
]]>

and now the project can be loaded.

Unfortunately, it is obvious that the problem was in the code which generated this wrong transition, not in the code mentioned in the stack backtrace (although there could have been some check for list bounds in this code).

(I don't know how to format XML here in the post, so I atach the diff of old and corrected files.)

SpatMan, I don't think this is the same problem, only symptoms are same.
Your crash is within MLT.