Bug 71281 - crash in ~ClassifierCodeDocument() on unedited file
Summary: crash in ~ClassifierCodeDocument() on unedited file
Status: RESOLVED FIXED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: HI crash
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-27 02:51 UTC by Jonathan Riddell
Modified: 2004-02-17 23:30 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathan Riddell 2003-12-27 02:51:45 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources

Open a complicated document and close it again without any edits and it crashes.

#0  0x40bc5737 in QObject::disconnectInternal(QObject const*, int, QObject const*, int, int) () from /usr/lib/libqt-mt.so.3
#1  0x40bc557c in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) ()
   from /usr/lib/libqt-mt.so.3
#2  0x0813d613 in OwnedCodeBlock::release() (this=0x40fc37f4) at qobject.h:240
#3  0x0813e8e7 in OwnedHierarchicalCodeBlock::release() (this=0x842f940) at ownedhierarchicalcodeblock.cpp:48
#4  0x0810c398 in CodeGenObjectWithTextBlocks::resetTextBlocks() (this=0x82cd7c8) at codegenobjectwithtextblocks.cpp:344
#5  0x0811d308 in HierarchicalCodeBlock::release() (this=0x842f3e0) at hierarchicalcodeblock.cpp:410
#6  0x0810c398 in CodeGenObjectWithTextBlocks::resetTextBlocks() (this=0x8443dd0) at codegenobjectwithtextblocks.cpp:344
#7  0x0810b420 in ~CodeGenObjectWithTextBlocks (this=0x8443dd0) at codegenobjectwithtextblocks.cpp:33
#8  0x08101e3b in ~CodeDocument (this=0x8443da8) at qstring.h:848
#9  0x080f3421 in ~ClassifierCodeDocument (this=0x8443da8) at qptrlist.h:70
#10 0x0825ab28 in ~CPPHeaderCodeDocument (this=0x8443da8) at qstring.h:848
#11 0x082510e8 in ~CPPCodeGenerator (this=0x8459bc0) at cppcodegenerator.cpp:43
#12 0x08157dfa in UMLDoc::removeCodeGenerator(CodeGenerator*) (this=0x83e99b0, remove_object=0x8459bc0) at umldoc.cpp:451
#13 0x08157b13 in UMLDoc::deleteContents() (this=0x83e99b0) at qdict.h:111
#14 0x08156985 in UMLDoc::saveModified() (this=0x83e99b0) at umldoc.cpp:185
#15 0x0814e06e in UMLApp::queryClose() (this=0x8327548) at uml.cpp:564
#16 0x4059a343 in KMainWindow::closeEvent(QCloseEvent*) () from /usr/lib/libkdeui.so.4
#17 0x40bf94d2 in QWidget::event(QEvent*) () from /usr/lib/libqt-mt.so.3
#18 0x40cab962 in QMainWindow::event(QEvent*) () from /usr/lib/libqt-mt.so.3
#19 0x40b6e57f in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3
#20 0x40b6db8b in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libqt-mt.so.3
#21 0x4076ff3f in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4
#22 0x40bf8ed5 in QWidget::close(bool) () from /usr/lib/libqt-mt.so.3
#23 0x40b0dd6c in QETWidget::translateCloseEvent(_XEvent const*) () from /usr/lib/libqt-mt.so.3
#24 0x40b0850c in QApplication::x11ClientMessage(QWidget*, _XEvent*, bool) () from /usr/lib/libqt-mt.so.3
#25 0x40b09456 in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libqt-mt.so.3
#26 0x40b1e321 in QEventLoop::processEvents(unsigned) () from /usr/lib/libqt-mt.so.3
#27 0x40b8039f in QEventLoop::enterLoop() () from /usr/lib/libqt-mt.so.3
#28 0x40b80254 in QEventLoop::exec() () from /usr/lib/libqt-mt.so.3
#29 0x40b6e7c1 in QApplication::exec() () from /usr/lib/libqt-mt.so.3
#30 0x08133e4e in main (argc=327684, argv=0x50004) at main.cpp:86
Comment 1 Oliver Kellogg 2004-01-06 05:35:12 UTC
Jonathan,

quanta.xmi does not prompt a crash for me.
Could you create an attachment for this?

Thanks,
Oliver
Comment 2 Jonathan Riddell 2004-01-07 00:00:38 UTC
It affects this diagram

http://muse.19inch.net/~jr/tmp/control_ingresos_gastos.xmi

Seems to be OK if you load it normally but if it loads up as the default diagram on startup I get various backtraces from closing Umbrello or after loading a new file.

Quite maddening.
Comment 3 Brian Thomas 2004-02-17 23:30:08 UTC
I dont see this error; I just opened this file, then closed it
with no problems.

I believe this was fixed in the recent patch cycle.