> On Oct 26, 2018, at 7:36 PM, prl <[email protected]> wrote:
> 
> I've been having occasional crashes in GnuCash 3.3 on MacOS 10.11.6 (the Mac 
> is a MacBook Pro 13-inch, Mid 2009 and can't be upgraded to a more recent 
> MacOS version).
> 
> The crashes typically happen within the first few transactions that I enter 
> after starting GnuCash.
> 
> I've pressed "Report..."  the "GnuCash quit unexpectedly" a couple of times - 
> but that says it reports to Apple. Is that a useful way of getting the bug 
> info to the GnuCash devs?
> 
> Pressing "Reopen" in the popup doesn't seem to do anything. GnuCash isn't 
> re-opened. Restarting it normally from Finder starts it with the expected 
> GnuCask popup about the presence of the lock file.
> 
> I have the stack trace info for the most recent crash, but the gnucash.trace 
> file appears to have been overwritten when I restarted GnuCash to do what I 
> was actually trying to do at the time.
> 
> This is a snippet from the stack trace:
> 
> Exception Type:        EXC_CRASH (SIGABRT)
> Exception Codes:       0x0000000000000000, 0x0000000000000000
> Exception Note:        EXC_CORPSE_NOTIFY
> 
> Application Specific Information:
> *** Terminating app due to uncaught exception 'NSInvalidArgumentException', 
> reason: '-[_CFXNotificationObjectRegistration visibleFrame]: unrecognized 
> selector sent to instance 0x7f838051eac0'
> terminating with uncaught exception of type NSException
> abort() called
> 
> Application Specific Backtrace 1:
> 0   CoreFoundation                      0x00007fff980b0452 
> __exceptionPreprocess + 178
> 1   libobjc.A.dylib                     0x00007fff8c23d73c 
> objc_exception_throw + 48
> 2   CoreFoundation                      0x00007fff9811a18d 
> -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
> 3   CoreFoundation                      0x00007fff980204c1 ___forwarding___ + 
> 1009
> 4   CoreFoundation                      0x00007fff980c4a48 
> __forwarding_prep_1___ + 120
> 5   libgdk-3.0.dylib                    0x000000010fb60d02 
> gdk_quartz_monitor_get_workarea + 98
> 6   libgtk-3.0.dylib                    0x000000010f74744f 
> gtk_window_guess_default_size + 79
> 7   libgtk-3.0.dylib                    0x000000010f74116b 
> gtk_window_compute_configure_request + 299
> 8   libgtk-3.0.dylib                    0x000000010f74a921 gtk_window_realize 
> + 641
> 9   libgobject-2.0.0.dylib              0x000000010ff1da0a 
> _g_closure_invoke_va + 314
> 10  libgobject-2.0.0.dylib              0x000000010ff35831 
> g_signal_emit_valist + 1521
> 11  libgobject-2.0.0.dylib              0x000000010ff36216 g_signal_emit + 134
> 12  libgtk-3.0.dylib                    0x000000010f727c81 gtk_widget_realize 
> + 257
> 13  libgtk-3.0.dylib                    0x000000010f6e4b54 
> gtk_tooltip_show_tooltip + 436
> 14  libgtk-3.0.dylib                    0x000000010f6e517c 
> tooltip_popup_timeout + 44
> 15  libgdk-3.0.dylib                    0x000000010fb27992 
> gdk_threads_dispatch + 50
> ...
> 
> Does this look like a known bug? I searched GnuCash Bugzilla for 
> "_CFXNotificationObjectRegistration visibleFrame" and "" it didn't find 
> anything useful.
> 
> It doesn't appear to be the same bug as 
> https://bugs.gnucash.org/show_bug.cgi?id=796656
> 
> I haven't been able to work out a reliable set of actions to trigger the bug.
> 
> I'm happy to make a Bugzilla report - is there anything useful I can put in 
> the report apart from the stack trace and gnucash.trace files?
> 

Nope, Apple doesn’t forward crash reports to us.

Yup, it’s a known bug, see https://bugs.gnucash.org/show_bug.cgi?id=796889 
<https://bugs.gnucash.org/show_bug.cgi?id=796889>.

Regards,
John Ralls


_______________________________________________
gnucash-user mailing list
[email protected]
To update your subscription preferences or to unsubscribe:
https://lists.gnucash.org/mailman/listinfo/gnucash-user
If you are using Nabble or Gmane, please see 
https://wiki.gnucash.org/wiki/Mailing_Lists for more information.
-----
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Reply via email to