[Uml-devel] [Bug 84828] New: umbrello crashes, becomes unstable freezes in load/save/autosave with large drawing size

[James McGuigan]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=84828      
           Summary: umbrello crashes, becomes unstable freezes in
                    load/save/autosave with large drawing size
           Product: umbrello
           Version: unspecified
          Platform: Gentoo Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: umbrello-devel.kde.org
        ReportedBy: james worldfuturecouncil org


Version:            (using KDE KDE 3.2.2)
Installed from:    Gentoo Packages
Compiler:          gcc 3.3.3 
OS:                Linux

Start with two classes in a class diagram, they are associated and the association has labeled multiplicities. Occasionally when moving one of these classes (to another point in the drawing) one of the labels on the association (usually the multiplicity label) will start shooting off in a random direction (Though usually towards the bottom right hand corner). This has the side effect of massivly increasing the "grid area" of the diagram (as it can move many screens away into the corner).

The workaround for this is to "Select All" and move all the objects a fraction, this resets all the label positions. It could also be done by just selecting both objects on either end of the association and moving them a fraction (Though its not always clear which association a displaced label is refering to).

Once a massive drawing (in terms of "grid area") has been created as part of the file, it seems to cause several problems such as crashing and becoming unstable. Also the program tends to freezes during load/save/autosave and this can take (upto a few minutes).

This seems to affect the program as long as such a file is loaded, even if its not being directly worked upon. I suffered this problem for quite a long time, before realizing I had two or three very large area class diagrams in the file. It made the program almost unusable.

Having deleted some of these diagrams and fixed the problem in the reming one, the program seems a little more responsive, though as I only noticed this "solution" as I was cleaning up the "final verson" for my project, I havn't used the program that much since so I cannot confirm this 100% solves the problems (but it seems to).

I hope this helps locate the underlying bug thats causing this.