GNOME Bugzilla – Bug 151696
Crash with Navigation Window
Last modified: 2006-08-19 14:54:47 UTC
From: Andrew Bennetts <andrew-bugbuddy@puzzling.org> To: submit@bugs.gnome.org X-Mailer: bug-buddy 2.7.91 Subject: Crash quickly reclicking on the mini-preview window Distribution: Debian testing/unstable Package: dia Severity: normal Version: GNOME2.7.92 0.93 Gnome-Distributor: Ubuntu Synopsis: Crash quickly reclicking on the mini-preview window Bugzilla-Product: dia Bugzilla-Component: general Bugzilla-Version: 0.93 BugBuddy-GnomeVersion: 2.0 (2.7.92) Description: Description of the crash: (I'm not sure what the right terminology is; there's a little preview window that's accessible by clicking at the bottom-right corner of a diagram's window which can be used to pan around the diagram quickly. That's what I'm referring to when I say "preview window") Quickly clicking on the preview window repeatedly, so that it doesn't have time to redraw, caused dia to crash for me. I did this by accidentally letting go of my mouse button, and very quickly clicking it again. Steps to reproduce the crash: 1. Open a diagram (this one is relatively complex, roughly 20 interconnected boxes from the UML set) 2. Click and hold on the bottom right of the window to bring up the preview window, and then very quickly release and then click and hold again Expected Results: No crash :) How often does this happen? This is the first time I've seen it, so it might be quite rare. Additional Information: $ dpkg -l dia-gnome | grep dia ii dia-gnome 0.93-4ubuntu2 Diagram editor (GNOME version) Debugging Information: Backtrace was generated from '/usr/bin/dia' (no debugging symbols found)...Using host libthread_db library "/lib/tls/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread 1088382688 (LWP 7608)] (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)...(no debugging symbols found)...(no debugging symbols found)...0x40ac2f2e in __waitpid_nocancel () from /lib/tls/libpthread.so.0
+ Trace 49838
Thread 1 (Thread 1088382688 (LWP 7608))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-09-02 12:16 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "dia". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was andrew@fuchsia.puzzling.org. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
fixed subject
Managed to reproduce by clicking *many* times quickly. Top of stack trace:
+ Trace 61789
Ubuntu bug about this: http://bugzilla.ubuntu.com/show_bug.cgi?id=14545 no need to click clicking to get the crash using dia 0.94-11 package with GNOME 2.12 on current Ubuntu. Backtrace of the crash: (dia:2133): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (ob ject)' failed (dia:2133): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (ob ject)' failed sys:1: GtkWarning: gtk_widget_destroy: assertion `GTK_IS_WIDGET (widget)' failed (dia:2133): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (ob ject)' failed Program received signal SIGSEGV, Segmentation fault.
+ Trace 62960
Thread NaN (LWP 2133)
*** Bug 303388 has been marked as a duplicate of this bug. ***
With gtk+ > 2.6.x it seems to reliably crash every single time. Which should make it an easy fix ;) It seems as if I've already found a work-around, not sure if this issue also should be reported as gtk bug. But apparently it was possible to make the release_event handler called twice in earlier versions, too.
2005-12-27 Hans Breuer <hans@breuer.org> * app/navigation.c : protect on_da_button_release_event() against being called twice. Also only popdown the navigation window after the first draw (reusing nav->is_first_expose). Fixes bug #151696
*** Bug 322582 has been marked as a duplicate of this bug. ***
*** Bug 317911 has been marked as a duplicate of this bug. ***
*** Bug 326664 has been marked as a duplicate of this bug. ***
*** Bug 328278 has been marked as a duplicate of this bug. ***
*** Bug 328895 has been marked as a duplicate of this bug. ***
*** Bug 331570 has been marked as a duplicate of this bug. ***
*** Bug 336593 has been marked as a duplicate of this bug. ***
*** Bug 339176 has been marked as a duplicate of this bug. ***
*** Bug 348039 has been marked as a duplicate of this bug. ***
*** Bug 352038 has been marked as a duplicate of this bug. ***