GNOME Bugzilla – Bug 129022
Dia crashed when moving an object after adjusting page margins
Last modified: 2014-06-11 17:55:32 UTC
Distribution: Unknown Package: dia Severity: critical Version: GNOME2.4.0 0.92 Gnome-Distributor: Gentoo Linux Synopsis: Dia crashed when moving an object after adjusting page margins Bugzilla-Product: dia Bugzilla-Component: general Bugzilla-Version: 0.92 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: I was not happy with the default page margin of 2.54 cm. I made the margin smaller. I then went back to my diagram and moved the only object on the page closer to the edge. Dia crashed. Steps to reproduce the crash: 1. I was unable to duplicate (sorry) 2. 3. Expected Results: How often does this happen? Only once so far Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/dia' (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)...[New Thread 16384 (LWP 1689)] (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)... (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)... 0x40ad385b in waitpid () from /lib/libpthread.so.0
+ Trace 42525
Thread 1 (Thread 16384 (LWP 1689))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-12-10 14:48 ------- Reassigning to the default owner of the component, dia-maint@bugzilla.gnome.org.
Appears to be a unique stack trace, according to the simple-dup-finder.
Can't reproduce this, either. May have something do do with parenting & undo, rather than margins. Seeing the diagram in question would be a help.
*** Bug 156706 has been marked as a duplicate of this bug. ***
The stack trace looks suspiciously like some of the ones with UML Class problems (list being updated during destruction) which have been reported elsewhere (bug #324754)
Not expecting any more info. Please try 0.95 which is supposed to be much more stable.
This probelm seems to be back, after a fashion. A few days ago, I started my first UML drawing with Dia and I notice Dia crashes occationally. Today I switched to my own build from the Dia git repository, because I desperately want the new feature to adjust the font size of UML "aggregations" and "generalizations". Now, that I can draw my models in their "true"/intended size, it became sensible to adjust the page margins to their actual values (of the document in which I am going to use the images). To determine the actual magin dimensions I want, used a series of resize, trail and error. While doing that, Dia crashed at about every other "move UML object after changing page margins"-attempt. I have been using Dia in the versions it's been shipping with Debian and/or Ubuntu for years and it never crashed on me. Crahses happen only when doing UML. The git-version I'm using is from this morning CEST, `git rev-parse HEAD` says ceb7265b65ed969698c358a850f8ff3ad42cc9d5. As far as I can tell the crashes occur with UML only and most frequently when changing page margins is involved. However, I cannot deterministically reproduce the problem. Is there any kind of trace/debug mode I can compile and run dia, so that I can provide useful data when this happens again? I think I'll be drawing UML for another few weeks.
./configure --enable-debug=yes but please don't let us resurrect an 11 year old bug. A new one with the version info would be much more appropriate.