inkscape @1.1.2_0+quartz builds, but crashes on startup

[hmeine (Hans Meine)]

As a follow-up to #57641, I was trying an inkscape +quartz build on a new MacPorts installation on a new MacBook Pro with M1 processor and Monterey 12.2.1. The build experience was very satisfying, but inkscape crashes on startup with SIGTRAP.

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000001, 0x0000000186724b6c
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process:   exc handler [29480]

Application Specific Information:
dyld4 config: DYLD_LIBRARY_PATH=
detected buffer overflow


Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_c.dylib             	       0x186724b6c __chk_fail_overflow + 24
1   libsystem_c.dylib             	       0x1866b3b30 __memmove_chk + 40
2   libgtk-3.0.dylib              	       0x10850d7e4 _gtk_marshal_VOID__STRING_STRINGv + 56
3   libgobject-2.0.0.dylib        	       0x10571d200 _g_closure_invoke_va + 224
4   libgobject-2.0.0.dylib        	       0x105732498 g_signal_emit_valist + 852
5   libgobject-2.0.0.dylib        	       0x105732ce4 g_signal_emit + 28
6   libgtk-3.0.dylib              	       0x1082707b4 gtk_action_muxer_primary_accel_changed + 128
7   libgtk-3.0.dylib              	       0x108286d9c gtk_application_set_accels_for_action + 132
8   libgtk-3.0.dylib              	       0x1084fe9dc gtk_application_impl_quartz_startup + 212
9   libgtk-3.0.dylib              	       0x1082883d4 gtk_application_startup + 124
10  libgobject-2.0.0.dylib        	       0x10571d200 _g_closure_invoke_va + 224
11  libgobject-2.0.0.dylib        	       0x105732498 g_signal_emit_valist + 852
12  libgobject-2.0.0.dylib        	       0x105732ce4 g_signal_emit + 28
13  libgio-2.0.0.dylib            	       0x105f868a8 g_application_register + 244
14  libgiomm-2.4.1.dylib          	       0x107c43cc4 Gio::Application::register_application() + 44
15  libinkscape_base.dylib        	       0x106cfee68 InkscapeApplication::InkscapeApplication() + 7432
16  libinkscape_base.dylib        	       0x106cfcf30 InkscapeApplication::singleton() + 40
17  inkscape                      	       0x104f1a9dc main + 6636
18  dyld                          	       0x1053250f4 start + 520

[jmroot (Joshua Root)]

Possibly a duplicate of #64377?

[hmeine (Hans Meine)]

I could not find that ticket when searching myself, but looking at the context could be related. However, what makes me wonder is that it seems to be about a build / configure error, while my build went fine, only I get a crash on startup.

Maybe I should have given this list of dependencies as well:

% port installed rdepof:inkscape and variant:quartz
The following ports are currently installed:
  cairo @1.17.4_0+quartz+universal (active)
  cairomm @1.12.2_0+quartz (active)
  glib2 @2.64.6_1+quartz+universal (active)
  glibmm @2.62.0_0+quartz (active)
  gspell @1.8.4_1+quartz (active)
  gtk3 @3.24.31_0+quartz (active)
  gtkmm3 @3.24.2_0+quartz (active)
  gtksourceview3 @3.24.11_1+quartz (active)
  librsvg @2.52.6_0+quartz (active)
  pango @1.50.4_0+quartz (active)
  pangomm @2.42.1_1+quartz (active)

[evanmiller (Evan Miller)]

Looks like a duplicate rather of #64319. @mascguy, looks like a patch is missing in gtk3?

[hmeine (Hans Meine)]

That's true, that looks like a duplicate, at least when considering the later comments. Unfortunately, the title & initial description are not related to this at all (I am building on MacOS 12). Not sure how to proceed; I feel like it would make sense to close #64319 (or to keep it open if the initial idea of applying the patch unconditionally is still relevant – not sure if this is now irrelevant) and to retitle this one which may not be specific to inkscape in the first place.

[mascguy (Christopher Nielsen)]

Replying to evanmiller:

Looks like a duplicate rather of #64319. @mascguy, looks like a patch is missing in gtk3?

I'll have to go back and review, but I believe the patch is included in upstream's release for gtk3 3.24.31. (And our gtk3 port has been updated to that version.) It's always possible that I missed something, though.

As for this overall issue, still pondering where to go from here. Thoughts/suggestions welcome!

[evanmiller (Evan Miller)]

Replying to mascguy:

Replying to evanmiller:

Looks like a duplicate rather of #64319. @mascguy, looks like a patch is missing in gtk3?

I'll have to go back and review, but I believe the patch is included in upstream's release for gtk3 3.24.31. (And our gtk3 port has been updated to that version.) It's always possible that I missed something, though.

As for this overall issue, still pondering where to go from here. Thoughts/suggestions welcome!

It looks like perhaps the patch was included – but now there is a different issue (i.e. this issue and comment:ticket:64319:3) that surfaced in 3.24.31. It will need to be researched as it potentially affects all GTK3 apps on arm64.

[mascguy (Christopher Nielsen)]

Hans, are you still seeing a crash with the latest Inkscape release (1.2.0)?

[hmeine (Hans Meine)]

I am currently running inkscape @1.1.2_2+quartz, and even that does not show the problem anymore. That is, I also run the discussed gtk3 version:

  cairo @1.17.4_0+quartz+universal (active)
  cairomm @1.12.2_0+quartz (active)
  glib2 @2.64.6_2+quartz+universal (active)
  glibmm @2.62.0_0+quartz (active)
  gspell @1.8.4_1+quartz (active)
  gtk3 @3.24.31_1+quartz (active)
  gtkmm3 @3.24.2_0+quartz (active)
  gtksourceview3 @3.24.11_1+quartz (active)
  librsvg @2.52.6_0+quartz (active)
  pango @1.50.7_0+quartz (active)
  pangomm @2.42.1_1+quartz (active)

I will try out Inkscape 1.2.0 as well, but it looks as if this ticket can be closed already.

[mascguy (Christopher Nielsen)]

Replying to hmeine:

I am currently running inkscape @1.1.2_2+quartz, and even that does not show the problem anymore.

I will try out Inkscape 1.2.0 as well, but it looks as if this ticket can be closed already.

Great, glad the issue is resolved!