Re: [gtk-osx-users] Crash issue

[Miroslav Rajcic <mrajcic hotmail com>]

Hi John,

NoteCase Pro is my app.

The issue with debugging is that it works fine here, but it crashes on users PC.

User may not be technical person, but he took the trouble to send crash log with his description.

I am not familiar with Apple development in detail (Cocoa framework), but the facts are:

- my code uses plain GTK/GtkSourceView calls

- the only Apple-custom code is the integration with Finder (support to open document from Finder) as described on GTK-OSX wiki pages

- GTK used is the one built by jhbuild, I see no issues here

- in my Makefile, I only link against libs returned by "pkg-config --libs gtk+-2.0 glib-2.0 gthread-2.0 gio-2.0  gtksourceview-2.0 gtk-mac-integration" result

So I am not sure where Cocoa could come into play here.

Regards,

  Miroslav

---

From: John Ralls <jralls ceridwen us>
Sent: Sunday, January 17, 2016 5:03 PM
To: Miroslav Rajcic
Cc: gtk-osx-users-list gnome org
Subject: Re: [gtk-osx-users] Crash issue

 

On Jan 17, 2016, at 12:16 AM, Miroslav Rajcic <mrajcic hotmail com> wrote:

I got a crash report from a user using my GTK2.x based app , so I though to ask here if anyone can recognize if this is a known issue (never got this before).

My app was built using GTK 2.24.28 (built on OSX version 10.7.5, XCode 4.2 (gcc 4.2.1), using modulesets-stable, 

using jhbuild setting "setup_sdk(target="10.6", sdk_version="10.6", architectures=["i386"])").

The crash happens OSX version 10.11.2 (El Capitan).

In users words:

"I am not sure if it is related but I had been using NoteCase Pro alongside the Calendar app, with both on thesame screen, using the Split View function.  I believe Split View is new in El Capitan version of OS X.

It is a little difficult to use these two applications together in Split View, but to be fair I have also found that I have similar difficulties with LibreOffice and Mail."

As I can see in my log, app was not used in full screen mode, but the stack trace mentions some "FullScreen" related functions.

Stack backtrace follows:

17:27:44.857 2   notecase-bin                        0x0050cf08 signal_handler + 40 ()
17:27:44.857 3   libsystem_platform.dylib            0x9d65f01b _sigtramp + 43 ()
17:27:44.857 4   ???                                 0xffffffff 0x0 + 4294967295 ()
17:27:44.857 5   libgdk-quartz-2.0.0.dylib           0x00fbcfb4 -[GdkQuartzView setFrame:] + 148 ()
17:27:44.857 6   AppKit                              0x9e1fb717 -[NSThemeFrame setStyleMask:] + 1047 ()
17:27:44.857 7   AppKit                              0x9e1fb1b3 __25-[NSWindow setStyleMask:]_block_invoke + 2181 ()
17:27:44.857 8   AppKit                              0x9e92dde1 NSPerformVisuallyAtomicChange + 212 ()
17:27:44.857 9   AppKit                              0x9e1fa8e0 -[NSWindow setStyleMask:] + 209 ()
17:27:44.857 10  AppKit                              0x9e395ec3 -[NSWindow _didExitFullScreen:] + 342 ()
17:27:44.857 11  AppKit                              0x9ea7212f __123-[_NSWindowFullScreenTransition _performExitFullScreenModeForWindow:windowController:options:customWindows:doKitAnimation:]_block_invoke_2 + 504 ()
17:27:44.857 12  AppKit                              0x9ea71ded __123-[_NSWindowFullScreenTransition _performExitFullScreenModeForWindow:windowController:options:customWindows:doKitAnimation:]_block_invoke + 1440 ()
17:27:44.857 13  AppKit                              0x9e95e817 __177-[NSDockConnection(FullScreenMessages) sendFullScreenExitForTransition:synchronous:window:exitForClose:backgroundWindows:participatingWindows:customAnimation:completionHandler:]_block_invoke + 79 (FullScreenMessages) sendFullScreenExitForTransition:synchronous:window:exitForClose:backgroundWindows:participatingWindows:customAnimation:completionHandler:]_block_invoke ())
17:27:44.857 14  AppKit                              0x9e95c05f __57-[NSDockConnection sendMessage:synchronous:replyHandler:]_block_invoke_2 + 98 ()
17:27:44.857 15  libxpc.dylib                        0x91925861 _xpc_connection_reply_callout + 31 ()
17:27:44.857 16  libxpc.dylib                        0x91925803 _xpc_connection_call_reply + 32 ()
17:27:44.857 17  libdispatch.dylib                   0x943e9763 _dispatch_client_callout + 50 ()
17:27:44.857 18  libdispatch.dylib                   0x943fdf9b _dispatch_main_queue_callback_4CF + 1672 ()
17:27:44.857 19  CoreFoundation                      0x9c4a292e __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 14 ()

So my question is: is this a known issue? Any tip or idea to help me with this?

Is Notebook Pro your app? If not, tell the user to go bug them. If so, how the heck is GdkQuartzView getting called from inside AppKit in a program controlled by the Cocoa run loop?

Regards,

John Ralls