SIGSEGV recieved on hiding dock

[dopelover]

Inkscape recieves SIGSEGV always when I try to hide dock tahat consists of two or more dialogs. Inkscape must be in fullscreen mode.

How to reproduce:
1) Launch Inkscape
2) Create dock that consists of two dialogs (see screenshot).
3) Switch Inkscape to fullscreen mode.
3) Hit F12 or click Viev>Show/Hide Dialogs.

Inkscabe should recieve SIGSIEG.

I use Inkscape r21198 runing on Ubuntu 9.04.

[Thomas Ibbotson (thomas-ibbotson)]

I can confirm this using Ubuntu Intrepid 64bit with SVN 21198.

[Diederik van Lierop (mail-diedenrezi)]

Cannot reproduce this on Fedora 10, using rev. 21251

[dopelover (dopelover)]

This bug is still present in recent developement version. Any chance to solve it until releasing 0.47?

[Pablo Trabajos (pajarico)]

Maybe is a specific Linux bug. Can't reproduce it on windows XP SP3 and 0.47pre3. However, I had a really hard time to place docks like that, placing Fill & Stroke and Layers one above the other on a separate dock was nigh impossible. Then I hit F11 (fullscreen), and then F12 (hide dialogs) and then back. Problems:
* it didn't come back from fullscreen.
* dialogs are not correctly restored when coming back from F12. Dialogs placed side by side or on a floating dock are restored at the right of the screen (as usual).

But it never crashes.

People with problems should report us what window manager and X version are they using.

[dopelover (dopelover)]

It is rather not Linux linux specific problem. I have also tried to reproduce the crash with most recent Windows build I found (Inkscape 0.46+devel 22040, built Aug 10 2009) and it also crashes on Windows Vista SP1. On my Linux box I have tried to reproduce the crash running Inkscape with Cmpiz and OpenBox. Both window managers and X sever were installed from official Ubuntu 9.04 repository. Changing window manager doesn't solve the problem.

[su_v (suv-lp)]

I can reproduce a crash (but not in a consistent way) with
Inkscape 0.46+devel r22413
OS X 10.5.8 with X11/XQuartz 2.4.0 (xorg-server 1.5.3-apple14)
GTK+ version: 2.16.5

1) Inkscape on OS X doesn't keep 2 dialogs in a detached (floating) dock when using Show/Hide Dialogs <F12> in fullscreen mode: one of them is re-attached (docked) to the main window (tried with several combinations - it is not bound to a certain dialog window).
2) The crashes occur in different situations, sometimes I could trigger one when using <F12> in fullscreen mode, with one dialog in a detached dock. Other times Inkscape crashed when quitting with still opened dialogs in the detached (floating) dock. Or when re-attaching the second dialog to the detached (floating) dock (in fulscreen mode).
3) Overall the handling of detached dialogs as well as floating (set via preferences) dialog windows feels erratic and error-prone (IMHO).

The related crash reports I get on OS X start similar to this:

Thread 0 Crashed:
0 libgtkmm-2.4.1.dylib 0x00e93be8 Gtk::Window::get_size(int&, int&) const + 8
1 inkscape-bin 0x004987e7 Inkscape::UI::Dialog::Dialog::save_geometry() + 71
2 inkscape-bin 0x0049ff35 Inkscape::UI::Dialog::Behavior::DockBehavior::onHideF12() + 21
3 libgobject-2.0.0.dylib 0x01cb8b29 g_closure_invoke + 313
4 libgobject-2.0.0.dylib 0x01cc939c signal_emit_unlocked_R + 1900
5 libgobject-2.0.0.dylib 0x01ccaa4d g_signal_emit_valist + 1853
6 libgobject-2.0.0.dylib 0x01ccadb9 g_signal_emit + 41
7 inkscape-bin 0x000975bc inkscape_dialogs_toggle() + 92
8 inkscape-bin 0x0031b382 sp_action_perform(SPAction*, void*) + 530
9 inkscape-bin 0x0011eaf3 sp_shortcut_invoke(unsigned int, Inkscape::UI::View::View*) + 83
10 inkscape-bin 0x0032be9c on_window_key_press(_GdkEventKey*) + 92
11 inkscape-bin 0x0032c1a7 sigc::internal::slot_call1<sigc::pointer_functor1<_GdkEventKey*, bool>, bool, _GdkEventKey*>::call_it(sigc::internal::slot_rep*, _GdkEventKey* const&) + 23
12 libgtkmm-2.4.1.dylib 0x00e90a81 (anonymous namespace)::Widget_signal_key_press_event_callback(_GtkWidget*, _GdkEventKey*, void*) + 65
13 libgtk-x11-2.0.0.dylib 0x014cc01b _gtk_marshal_BOOLEAN__BOXED + 107
14 libgobject-2.0.0.dylib 0x01cb8b29 g_closure_invoke + 313
15 libgobject-2.0.0.dylib 0x01cc9714 signal_emit_unlocked_R + 2788
16 libgobject-2.0.0.dylib 0x01cca4c7 g_signal_emit_valist + 439
17 libgobject-2.0.0.dylib 0x01ccadb9 g_signal_emit + 41
18 libgtk-x11-2.0.0.dylib 0x015eb046 gtk_widget_event_internal + 614
19 libgtk-x11-2.0.0.dylib 0x014ca312 gtk_propagate_event + 482
20 libgtk-x11-2.0.0.dylib 0x014ca79f gtk_main_do_event + 1151
21 libgdk-x11-2.0.0.dylib 0x018202c5 gdk_event_dispatch + 85
22 libglib-2.0.0.dylib 0x01d2cf0d g_main_context_dispatch + 573
23 libglib-2.0.0.dylib 0x01d307bb g_main_context_iterate + 1179
24 libglib-2.0.0.dylib 0x01d30a97 g_main_loop_run + 439
25 libgtk-x11-2.0.0.dylib ...

[su_v (suv-lp)]

Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_INVALID_ADDRESS at address: 0xc0000003

[dopelover (dopelover)]

This bug is still present in current development version (Inkscape 0.47+devel r9058)

[Beluga (buovjaga)]

Could not reproduce with GTK3. Please re-test.

Arch Linux 64-bit, KDE Plasma 5
Inkscape 0.92pre1 15054 (GTK3)

[Qantas94Heavy (qantas94heavy)]

Cannot reproduce with Inkscape 0.92.3 on Windows 10 64-bit. Due to age of report and that previous tester also could not reproduce, closing as fixed.

If you still have a similar issue with the latest version of Inkscape, please file a bug on our new GitLab tracker: https://inkscape.org/report. Thank you!

Closed by: https://gitlab.com/Qantas94Heavy