Bug 111731 - Frequent Crashes when editing with "VPL & Source Editor" open
Summary: Frequent Crashes when editing with "VPL & Source Editor" open
Status: RESOLVED FIXED
Alias: None
Product: quanta
Classification: Unmaintained
Component: VPL (show other bugs)
Version: 3.4.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Paulo Moura Guedes
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-29 22:59 UTC by Tom Mealey
Modified: 2005-10-01 18:49 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Mealey 2005-08-29 22:59:26 UTC
Version:           3.4.2 (using KDE KDE 3.4.1)
Installed from:    Compiled From Sources
Compiler:          GCC 4.0.1 
OS:                Linux

I've had this happen several times already.  When I have the VPL & Source Editor open and am editing a page... after several edits the application crashes.  I am using quanta through an X session over a network... (app is running on one machine... display on another)  Can anyone point me in the right direction?


Here is a copy of the backtrace:

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1209084224 (LWP 4168)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#4  0x0814f9c3 in Node::~Node ()
#5  0x082ce449 in NodeModif::~NodeModif ()
#6  0x082d2902 in QPtrList<NodeModif>::deleteItem ()
#7  0x02ca0a8d in QGList::clear () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#8  0x082ce76a in NodeModifsSet::~NodeModifsSet ()
#9  0x082d293e in QPtrList<NodeModifsSet>::deleteItem ()
#10 0x02ca0a8d in QGList::clear () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x082ce3ec in undoRedo::turnOn ()
#12 0x08099b59 in QuantaView::slotVPLGetFocus ()
#13 0x0809aba2 in QuantaView::qt_invoke ()
#14 0x029b3d57 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x029b4990 in QObject::activate_signal_bool ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x082abbfc in KafkaWidget::hasFocus ()
#17 0x082bd269 in KafkaWidget::eventFilter ()
#18 0x029b387c in QObject::activate_filters ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x029b38f1 in QObject::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x029f1dec in QWidget::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#21 0x0294f0cd in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#22 0x0294fa26 in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#23 0x00e917a1 in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0x029ef832 in QWidget::setFocus () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#25 0x0295023f in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#26 0x00e917a1 in KApplication::notify () from /usr/lib/libkdecore.so.4
#27 0x028e6746 in QETWidget::translateMouseEvent ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#28 0x028e4f01 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#29 0x028f9008 in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#30 0x02967772 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#31 0x02967696 in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#32 0x0294ea99 in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#33 0x0809f299 in main ()
Comment 1 András Manţia 2005-09-14 13:50:14 UTC
Is it possible to get an example file and the exact steps to reproduce 
the bug?
Comment 2 Tom Mealey 2005-09-15 15:03:28 UTC
Well, an example file would include any file... even starting from a blank page.  If I have it on split view... and start typing then switch to another application then back & forth etc... then type some more... the app crashes.  It appears pretty random unfortunately... but with an average bit of use, it usually happens within the first few minutes.

More info:
the KDE crash hanlder reports "The applicaion Quanta (quanta) crashed and caused the signal 6 (SIGABRT)."

In an xterm... (from where the application is launched) the message "terminate called after throwing an instance of 'DOM::DOMException'"
Comment 3 Tom Mealey 2005-09-19 22:01:11 UTC
Reciently updated KDE to 3.4.2 and problem still exists.
Comment 4 András Manţia 2005-09-19 22:24:38 UTC
If it's possible, you should try the 3.5 branch of the SVN version. I 
introduced many tests to catch the crashes, altough some might still 
happen. Again, a way to reproduce would help a lot.
Comment 5 Tom Mealey 2005-09-20 17:10:29 UTC
grr... the things I do to make things work.  Didn't know 3.5 requires unsermake and qt4 to compile it... too bad there was no pre-compiled version of qt4 for my distro :(   Oh well, enough complaining.   Compiler is running now.  I'll let you know the results as soon as my machine is done compiling qt 4 & kdewebdev 3.5.

Steps to reproduce:
  Open or create ANY document.  click the split vpl view, or the vpl only view... make changes ... make use control+home/control+end & scroll arround... make more changes... switch to other application... switch back... make more changes to document... and after several times of doing this... crash.  I'm trying to narrow down EXACTLY what combination causes this... but havn't found it yet.   On a side note... if you use the source-code view only... the app never crashes.
Comment 6 András Manţia 2005-09-20 17:29:14 UTC
[bugs.kde.org quoted mail]

You missread something, as 3.5 DOES NOT require unsermake, qt 4 and things
like that. You must have checked out the trunk instead of the 3.5 branch.
See http://quanta.kdewebdev.org/faq.php#faq13 .
At the end it says:
"The latest development version from the 3.x series is in
/home/kde/branches/KDE/3.5/kdewebdev. "

>   Open or create ANY document.  click the split vpl view, or the vpl only
> view... make changes ... make use control+home/control+end & scroll
> arround... make more changes... switch to other application... switch
> back... make more changes to document... and after several times of
> doing this... crash.  I'm trying to narrow down EXACTLY what combination
> causes this... but havn't found it yet.   On a side note... if you use
> the source-code view only... the app never crashes.


Sure, as this is about VPL, which is kind of a step-child since the
original author abandoned the Quanta project. Source-only mode is well
tested and constantly maintained and improved (mostly by me).
 And I saw crashes when swithcing between the modes and I fixed those, so
this is why I was asking for testing.
Comment 7 András Manţia 2005-10-01 18:49:51 UTC
I close the bug, as I believe it is fixed. Report if it present in the 
upcoming 3.4.3 or 3.5beta2 (well, or if you are able to compile the 3.5 
branch)