After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 665873 - Crash without error
Crash without error
Status: RESOLVED DUPLICATE of bug 611374
Product: dia
Classification: Other
Component: general
0.97.x
Other Linux
: Normal major
: ---
Assigned To: Dia maintainers
Dia maintainers
Depends on:
Blocks:
 
 
Reported: 2011-12-09 15:45 UTC by jochendemmer
Modified: 2011-12-11 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description jochendemmer 2011-12-09 15:45:56 UTC 
Open map, then I choose a tool (no matter which).
I begin to draw by clicking into the map, KEEPING the mouse button PRESSED.
Whilst holding i press the "del" key on my keyboard.
In the very moment I release the mouse button, DIA crashes.

All the effort drawing, kicked into the trashbin :-(
Comment 1 André Klapper 2011-12-11 14:49:58 UTC 
Thanks for taking the time to report this bug.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Comment 2 Hans Breuer 2011-12-11 15:18:27 UTC 
The bug is reproduceable, it was meant to be fixed by bug 611374 (but defenitely is not, i.e. the return statement is missing).
"Crash without error" is debatable - I'd say the error is in front of the keyboard ;) What exactly would be the purpose of deleting an object while creating them (or determining their initial size)?

No need for a stack trace, though.
Comment 3 Hans Breuer 2011-12-11 15:20:38 UTC 

*** This bug has been marked as a duplicate of bug 611374 ***
Comment 4 jochendemmer 2011-12-11 15:31:48 UTC 
That's very rude Hans, telling that "the user" would be the source of the problem. What's important for a good program is to be at least a little bit fault-tolerant. A crash with a following data loss is not something a user can really live with.
Deleting an object WHILE drawing could somehow be interpreted as:"oops, that's not what I wanted, so please don't actually draw it....". The ESC key doesn't do the trick.