Bug 375595 - sporadic crash after group undoing and redoing
Summary: sporadic crash after group undoing and redoing
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: git-master
Platform: Other Linux
: NOR major
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-26 19:35 UTC by farid
Modified: 2018-12-16 17:39 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
fritzibaby: timeline_corruption+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description farid 2017-01-26 19:35:49 UTC
(gdb) backtrace 
#0  0x00007fffefdf404f in raise () at /usr/lib/libc.so.6
#1  0x00007fffefdf547a in abort () at /usr/lib/libc.so.6
#2  0x00007fffefe31c50 in __libc_message () at /usr/lib/libc.so.6
#3  0x00007fffefe37fe6 in malloc_printerr () at /usr/lib/libc.so.6
#4  0x00007fffefe387de in _int_free () at /usr/lib/libc.so.6
#5  0x00007ffff31a54c7 in  () at /usr/lib/libQt5Xml.so.5
#6  0x00007ffff31af223 in  () at /usr/lib/libQt5Xml.so.5
#7  0x00007ffff31a541b in  () at /usr/lib/libQt5Xml.so.5
#8  0x00007ffff31af163 in  () at /usr/lib/libQt5Xml.so.5
#9  0x00007ffff31a64f6 in  () at /usr/lib/libQt5Xml.so.5
#10 0x00007ffff31a672a in  () at /usr/lib/libQt5Xml.so.5
#11 0x00007ffff31a6799 in  () at /usr/lib/libQt5Xml.so.5
#12 0x00007ffff31a541b in  () at /usr/lib/libQt5Xml.so.5
#13 0x00007ffff31a6799 in  () at /usr/lib/libQt5Xml.so.5
#14 0x000000000054e70f in QDomElement::~QDomElement() (this=0x7fffffffd6d0, __in_chrg=<optimized out>)
    at /usr/include/qt/QtXml/qdom.h:471
#15 0x000000000054e70f in ClipItem::setSelectedEffect(int) (this=this@entry=0x18b1e6f0, ix=1, 
    ix@entry=<error reading variable: Cannot access memory at address 0x7fffffffd79c>)
    at /tmp/yaourt-tmp-frd/aur-kdenlive-git/src/kdenlive/src/timeline/clipitem.cpp:276
#16 0x000000000057a2f2 in CustomTrackView::updateEffect(int, GenTime, QDomElement const&, bool, bool, bool) (this=0x4604800, track=<optimized out>, pos=..., insertedEffect=..., updateEffectStack=<optimized out>, replaceEffect=<optimized out>, refreshMonitor=<optimized out>)
    at /tmp/yaourt-tmp-frd/aur-kdenlive-git/src/kdenlive/src/timeline/customtrackview.cpp:2557
#17 0x00007ffff1e242ed in QUndoCommand::undo() () at /usr/lib/libQt5Widgets.so.5
#18 0x00007ffff1e24dcc in QUndoStack::undo() () at /usr/lib/libQt5Widgets.so.5
#19 0x00007ffff0a9e239 in QMetaObject::activate(QObject*, int, int, void**) ()
    at /usr/lib/libQt5Core.so.5
#20 0x00007ffff1aad992 in QAction::triggered(bool) () at /usr/lib/libQt5Widgets.so.5
#21 0x00007ffff1ab0380 in QAction::activate(QAction::ActionEvent) () at /usr/lib/libQt5Widgets.so.5
#22 0x00007ffff1ab0cfc in QAction::event(QEvent*) () at /usr/lib/libQt5Widgets.so.5
#23 0x00007ffff1ab435c in QApplicationPrivate::notify_helper(QObject*, QEvent*) ()
    at /usr/lib/libQt5Widgets.so.5
#24 0x00007ffff1abbad1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#25 0x00007ffff0a72a40 in QCoreApplication::notifyInternal2(QObject*, QEvent*) ()
    at /usr/lib/libQt5Core.so.5
#26 0x00007ffff0fe4d78 in QShortcutMap::dispatchEvent(QKeyEvent*) () at /usr/lib/libQt5Gui.so.5
---Type <return> to continue, or q <return> to quit---
#27 0x00007ffff0fe4e39 in QShortcutMap::tryShortcut(QKeyEvent*) () at /usr/lib/libQt5Gui.so.5
#28 0x00007ffff0f9d79d in QWindowSystemInterface::handleShortcutEvent(QWindow*, unsigned long, int, QFlags<Qt::KeyboardModifier>, unsigned int, unsigned int, unsigned int, QString const&, bool, unsigned short) () at /usr/lib/libQt5Gui.so.5
#29 0x00007ffff0fb4ca4 in QGuiApplicationPrivate::processKeyEvent(QWindowSystemInterfacePrivate::KeyEvent*) () at /usr/lib/libQt5Gui.so.5
#30 0x00007ffff0fba1c5 in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () at /usr/lib/libQt5Gui.so.5
#31 0x00007ffff0f9815b in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Gui.so.5
#32 0x00007fffdc5edda0 in  () at /usr/lib/libQt5XcbQpa.so.5
#33 0x00007fffe7d65587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#34 0x00007fffe7d657f0 in  () at /usr/lib/libglib-2.0.so.0
#35 0x00007fffe7d6589c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#36 0x00007ffff0ac746f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) ()
    at /usr/lib/libQt5Core.so.5
#37 0x00007ffff0a70e9a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) ()
    at /usr/lib/libQt5Core.so.5
#38 0x00007ffff0a7939c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#39 0x000000000048fbc6 in main(int, char**) (argc=<optimized out>, argv=<optimized out>)
    at /tmp/yaourt-tmp-frd/aur-kdenlive-git/src/kdenlive/src/main.cpp:160
Comment 1 Dany 2017-03-12 02:44:58 UTC
I confirm this bug. If you play some undo and redo in single/multi track, often it crash without bug report or insufficient report. This crash does not create automatic backups and I lost hours of work on clips because of this bug!
Comment 2 farid 2017-03-13 01:29:00 UTC
If (In reply to Dany from comment #1)
> I confirm this bug. If you play some undo and redo in single/multi track,
> often it crash without bug report or insufficient report. This crash does
> not create automatic backups and I lost hours of work on clips because of
> this bug!

If we could provide some instructions on how to reproduce this the devs can solve it. I havent been able to reproduce it.
Comment 3 Dany 2017-03-13 01:48:30 UTC
It isn't a specific way. If you have only one cutting clip in one track you can play undo/redo a lot of time, it does'n happen.
You have to cut, move tracks, add clips, add snippet of footage, invert their position, cut again, push "quikly" ctrl+z <-> ctrl+shift+z, add tasks and again undo and redo. In short, you need to have things on which to work on timeline and have an "heavy" history on cache.
Comment 4 Dany 2017-03-13 02:01:51 UTC
"Heavy" like a computational kdenlive work, maybe, I don't know. It'is happened many times to me. Many many times. Too many.
I work a lot with single clip, then I cut it in many little chunk which then I mix each other. Some titles, little effects... undo/redo and... boom! It crash!
Comment 5 farid 2017-03-13 15:47:33 UTC
(In reply to Dany from comment #4)
> "Heavy" like a computational kdenlive work, maybe, I don't know. It'is
> happened many times to me. Many many times. Too many.
> I work a lot with single clip, then I cut it in many little chunk which then
> I mix each other. Some titles, little effects... undo/redo and... boom! It
> crash!

I work with many many many clips and some compositing and have experienced this only a couple of times. That is why I haven't found a way to provide the instructions on how to cause the bug. Could it be due to dragging many clips in the timeline? Lets try to keep an eye on this... 

On the bright side, the timeline refactoring has started and when it is finished this bugs should be a thing of the past.

I am marking this as confirmed as more people have experienced it.
Comment 6 Dany 2017-03-13 16:03:20 UTC
Due to dragging many clips in the timeline? It depends on how "many" is intended. I work always with 3 video tracks and 2 audio tracks. In it I drag 2 or 3 video clips (chunked in about 30 pieces each one) and 2 sound tracks (1 voice + 1 music). Some .png, volume effect, 3 video transition and no more.
It is too heavy on Kdenlive? If it is, Kdenlive became unuseful...
Comment 7 farid 2017-03-13 16:10:54 UTC
(In reply to Dany from comment #6)
> Due to dragging many clips in the timeline? It depends on how "many" is
> intended. I work always with 3 video tracks and 2 audio tracks. In it I drag
> 2 or 3 video clips (chunked in about 30 pieces each one) and 2 sound tracks
> (1 voice + 1 music). Some .png, volume effect, 3 video transition and no
> more.

I usually drag more than those and it is fine... as I said there is something that is triggering the crash... finding it will make the fixing of the bug if not the refactoring should do it... 

> It is too heavy on Kdenlive? If it is, Kdenlive became unuseful...

I use it almost daily and is very useful to me. also almost all the bugs that i report get fixed. :)
Comment 8 Dany 2017-03-13 16:13:33 UTC
It is very useful for me too! It is because I wish this bug solved. I love Kdenlive!
Comment 9 Wegwerf 2017-03-13 19:39:29 UTC
Kdenlive usually handles many more timeline clips as I can confirm from my own projects: around 10-12 tracks with something like 200 timeline clips. I need to move them using the move tool when I'm finally adding in the opening intro and following title.
Comment 10 emohr 2018-11-18 17:46:24 UTC
Please try with the actual Kdenlive AppImage version 18.08.3
Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage
Comment 11 emohr 2018-12-16 16:48:34 UTC
Please try with the actual Kdenlive AppImage version 18.12.0b
Run the Appimage from the terminal (press CTRL + ALT + T). Move to the AppImage folder and run the .AppImage: ./Kdenlive*.AppImage
Comment 12 farid 2018-12-16 17:39:45 UTC
fixed in refactoring