It happens also just after entering the Practice mode (as in the bug 271626). It happens both with written practice and flashcard practice mode.

Hi Ansa,

Every 200 words sounds like a lot. Does this still happen with a modern Parley?  I know that the version number hasn't been updated as it should so I'm afraid you will have to give the general KDE version.

Thank you for looking into this. I have noticed that you have been recently very active and I really value the time you put into it.

I think the problem has disappeared in the meantime, because I am not aware of recent unexpected crashes during practice. However, I get crashes every time that I am running parley with a stylesheet and I exit practice prematurely (i.e. before I have practiced all words). It happens also with a small file.

I also sometimes experience crashes when I am adding images to the file by dragging them from my file manager. I suspect this might have to do with the size of my file (some 6000 lines with 5 columns and many links to audio and image files). So I learnt to save the file before adding any images (and just generally save it very often when I am editing it).

Please, let me know if I should file separate bugreports for these types of crashes.

Below is a backtrace for the crash with stylesheet. The stylesheet contains only one element:
QPushButton:focus {
 background-color:#C9DDF0;
 border:5px solid #C9DDF0;
}

I am currently running:

KDE Platform Version 4.12.2
Qt version 4.8.2.
Linux version 3.2.0-60-generic (buildd@allspice) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #91-Ubuntu SMP Wed Feb 19 03:55:18 UTC 2014
Ubuntu 12.04.4 LTS

Backtrace:
Application: Parley (parley), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb7774980 (LWP 5152))]

Thread 2 (Thread 0xb3456b40 (LWP 5154)):
#0  0x00437dcd in clock_gettime () from /lib/i386-linux-gnu/librt.so.1
#1  0x005223e5 in do_gettime (frac=0xb3455fb0, sec=0xb3455fa8) at tools/qelapsedtimer_unix.cpp:123
#2  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#3  0x0060c726 in QTimerInfoList::updateCurrentTime (this=0xb5302074) at kernel/qeventdispatcher_unix.cpp:343
#4  0x0060ca7a in QTimerInfoList::timerWait (this=0xb5302074, tm=...) at kernel/qeventdispatcher_unix.cpp:450
#5  0x0060b323 in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb34560bc) at kernel/qeventdispatcher_glib.cpp:136
#6  0x0060b3bd in timerSourcePrepare (source=0xb5302040, timeout=<optimized out>) at kernel/qeventdispatcher_glib.cpp:169
#7  0x03583832 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#8  0x03583f6f in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#9  0x035841c1 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#10 0x0060bde7 in QEventDispatcherGlib::processEvents (this=0xb5300468, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#11 0x005d76ad in QEventLoop::processEvents (this=0xb3456240, flags=...) at kernel/qeventloop.cpp:149
#12 0x005d7949 in QEventLoop::exec (this=0xb3456240, flags=...) at kernel/qeventloop.cpp:204
#13 0x004c0a1c in QThread::exec (this=0x92d6d90) at thread/qthread.cpp:501
#14 0x005b4cfd in QInotifyFileSystemWatcherEngine::run (this=0x92d6d90) at io/qfilesystemwatcher_inotify.cpp:248
#15 0x004c3eb0 in QThreadPrivate::start (arg=0x92d6d90) at thread/qthread_unix.cpp:307
#16 0x00b53d4c in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#17 0x03034bae in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb7774980 (LWP 5152)):
[KCrash Handler]
#7  0x00000000 in ?? ()
#8  0x064dc0b6 in QStyleSheetStyle::event (this=0xa539e60, e=0xbf985950) at styles/qstylesheetstyle.cpp:5798
#9  0x06162df4 in notify_helper (e=0xbf985950, receiver=0xa539e60, this=0x90f9d10) at kernel/qapplication.cpp:4556
#10 QApplicationPrivate::notify_helper (this=0x90f9d10, receiver=0xa539e60, e=0xbf985950) at kernel/qapplication.cpp:4528
#11 0x0616815d in QApplication::notify (this=0xbf985950, receiver=0xa539e60, e=0xbf985950) at kernel/qapplication.cpp:4285
#12 0x03903161 in KApplication::notify (this=0xbf987160, receiver=0xa539e60, event=0xbf985950) at ../../kdeui/kernel/kapplication.cpp:311
#13 0x005d8e0e in QCoreApplication::notifyInternal (this=0xbf987160, receiver=0xa539e60, event=0xbf985950) at kernel/qcoreapplication.cpp:915
#14 0x0616135c in sendEvent (event=0xbf985950, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#15 QApplicationPrivate::setFocusWidget (focus=0x0, reason=Qt::OtherFocusReason) at kernel/qapplication.cpp:2259
#16 0x061ab3fc in clearFocus (this=0xa73b528) at kernel/qwidget.cpp:6542
#17 QWidget::clearFocus (this=0xa73b528) at kernel/qwidget.cpp:6526
#18 0x061b6f19 in QWidget::~QWidget (this=0xa73b528, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1608
#19 0x065e8acf in QLineEdit::~QLineEdit (this=0xa73b528, __in_chrg=<optimized out>) at widgets/qlineedit.cpp:357
#20 0x039d2a9f in KLineEdit::~KLineEdit (this=0xa73b528, __in_chrg=<optimized out>) at ../../kdeui/widgets/klineedit.cpp:245
#21 0x039d2b32 in KLineEdit::~KLineEdit (this=0xa73b528, __in_chrg=<optimized out>) at ../../kdeui/widgets/klineedit.cpp:248
#22 0x005ee211 in QObjectPrivate::deleteChildren (this=0x96d8bb0) at kernel/qobject.cpp:1908
#23 0x061b6fcc in QWidget::~QWidget (this=0xab31408, __in_chrg=<optimized out>) at kernel/qwidget.cpp:1677
#24 0x080b5f0b in _start ()

Ok, thank you.  Good to know that the original crash seems gone.

But could you register one separate bug for each different type of crash?  The feature freeze for KDE SC 4.14 is today so we are done with feature development and will now focus on the bugs for a while until the release.  And crashes have extra high prio.

So if you register each crash you see, there's a bigger chance of getting them fixed. If nothing else, it won't be forgotten because one bug gets closed when a crash is fixed and there is another one in the same bug report.

Hi Ansa,

I may have missed it but I didn't see any new crash reports from the other crashes you mentioned.  We are going to try to fix all the crashes that we can before the release of the next version and the more data we can get the better chance we have.

But am I correct in thinking that this particular crash is fixed?  I haven't seen a crash during practice for a long time now but on the other hand I don't have any file with 6000 lines.  :)  I would like to close this one if possible so I'm grateful for an answer.

The crash when adding images is now registered separately as bug 332269. I am therefore closing this one since we haven't seen this particular crash for a while.

It's true, I have recently not had parley crashing. However, I noticed that (unintentionally), I have been using parley without the stylesheet, so that might have some effect. I will report a bug as soon as/if I get a crash! In the meantime, feel free to close this bugreport.

Oops, it seems I have accidentally undone your closing this bugreport... Sorry about that!

Haha, no problem.  Now re-closed.