Crash when closing Inkscape (reduced tools control bar)

Bug #1034788 reported by jazzynico
20
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Inkscape
Invalid
Medium
Unassigned

Bug Description

Reproduced on Debian Wheezy, Inkscape trunk revision 11595.
Reproduced on Windows XP, Inkscape trunk revision 11595 and 11098 and 0.48.3.1
Not reproduced on XP with 10923 and 0.48.2.

Steps:

1. Open inkscape and reduce its size so that the tools control bar hides some icons.
2. Click on the option drop down menu (triangle on Debian, arrows on XP).
3. Quit inkscape.

Result:
The console shows the following messages:
(inkscape.exe:3260): GLib-GObject-WARNING **: gsignal.c:2924: signal id `129' is invalid for instance `05C85BB0'
(inkscape.exe:3260): GLib-GObject-WARNING **: instance of invalid non-instantiatable type `(null)'
(inkscape.exe:3260): GLib-GObject-CRITICAL **: g_signal_emit_valist: assertion `G_TYPE_CHECK_INSTANCE (instance)' failed
and sometimes Inkscape crashes or (on XP) a process stays visible in the task manager eating 100% CPU.

Revision history for this message
jazzynico (jazzynico) wrote :

Backtrace from Debian with 11595 attached.

Changed in inkscape:
importance: Undecided → Medium
status: New → Triaged
tags: added: crash ui
Revision history for this message
su_v (suv-lp) wrote :

Warnings reproduced with Inkscape 0.48.2, 0.48.3.1 and current trunk r11598 on Mac OS X 10.5.8 (32bit) and OS X 10.7.4 (64bit):
- GTK+/X11 2.24.8 (Glib 2.28.8, gtkmm 2.24.0, libsigc++ 2.2.9)
- GTK+/Quartz 2.24.10 (Glib 2.28.8, gtkmm 2.24.2, libsigc++ 2.2.10)
- GTK+/X11 2.24.10 (Glib 2.32.4, gtkmm 2.24.2, libsigc++ 2.2.10)
- GTK3/X11 3.4.4 (Glib 2.32.4, gtkmm 3.4.0, libsigc++ 2.2.10)
- GTK+/Quartz 2.24.11 (Glib2 2.33.6, gtkmm 2.24.2, libsigc++ 2.2.10)
- GTK3/Quartz 3.5.10 (Glib 2.33.6, gtkmm 3.5.6, libsigc++ 2.2.10)

The warnings are not present with builds linked against older versions of the runtime dependencies (e.g. the official packages of Inkscape 0.47 and 0.48.x for Mac OS X).

Crashes or hangs (varies with all tested local builds) are not consistently reproducible for me (yet?): mostly they seem to occur when running Inkscape directly and less often (rarely) occur with the same steps/timing when launching a debug build from gdb. It also seems to differ depending on how strongly optimized the builds are.

Attaching a backtrace from a current GTK3/X11 3.4.4 debug build (which seems to include the most detailed debug information compared to other ones).

jazzynico (jazzynico)
tags: added: regression
Revision history for this message
jazzynico (jazzynico) wrote :

Reproduced again on Windows 7, with Inkscape trunk rev. 15007 (32-bit build).

Revision history for this message
Qantas94Heavy (qantas94heavy) wrote :

Could someone clarify how this should be reproduced? I can't seem to close Inkscape by the GUI or shortcut keys if the tool toolbar drop-down is open. Clicking elsewhere just closes the menu.

Changed in inkscape:
status: Triaged → Incomplete
Revision history for this message
Max Gaukler (mgmax) wrote :

Assuming fixed because there was no response. Please retest with the newest Inkscape version and report new issues in the new bug tracker: https://inkscape.org/report

Changed in inkscape:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.