Bug 153757 - crash when creating a message pointing to a certain class
Summary: crash when creating a message pointing to a certain class
Status: RESOLVED FIXED
Alias: None
Product: umbrello
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Umbrello Development Group
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-10 00:35 UTC by Anton Pussep
Modified: 2014-04-17 07:37 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.11.5


Attachments
the buggy file (51.54 KB, text/plain)
2007-12-10 00:37 UTC, Anton Pussep
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Anton Pussep 2007-12-10 00:35:40 UTC
Version:           1.5.71 (using KDE KDE 3.5.8)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When I create a message from any class pointing to a certain class in a sequence diagram, the CPU usage goes up to 100% for half a minute until the application crashes. The output is "Segmentation fault". I am going to attach the output log and the file to this bug report.
Comment 1 Anton Pussep 2007-12-10 00:37:00 UTC
Created attachment 22440 [details]
the buggy file

Open the file, choose "sequence diagram 2" and try to create a message that
points to "Condiment".
Comment 2 Anton Pussep 2007-12-10 00:42:18 UTC
The err output is:

umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: WARNING: returning 0 at UMLListView::findView
umbrello: ERROR: UMLClassifier::getOpList: class undef is parent of itself ?!?

whereas the last line appears for 30 MB. After that the application crashes printing "Segmentation fault". The KDE Crash Manager (or whatever it is called like) is not even started.
Comment 3 Christoph Feck 2011-12-20 02:58:33 UTC
This crash report is at least 4 years old and there were no further comments or status updates since then.

Therefore we believe that this crash is already fixed in KDE 4 or the backtrace is no longer applicable to KDE 4.

If the crash still happens with a recent KDE version (4.7.4 or 4.8), please add an updated backtrace or provide steps to reproduce. For more information, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

(To prevent automatic closing of this bug in the future, please set the bug status to ASSIGNED or NEW)
Comment 4 Ralf Habacker 2014-04-17 07:37:48 UTC
works in 4.11.5