ITOT any gesture which could be interpreted as the start of a scroll generated an immediate constrainBoundsRect call with +inf,+inf as the origin (apparently a bug/feature in Sierra). My custom NSClipView wasn't set up to handle the invalid coordinates (it generally passes back whatever is sent to it) which causes the crash. Replacing the origin with 0.0,0.0 fixes the problem, but that doesn't help with our existing software.
> On Nov 23, 2016, at 13:32 , Tom Doan <t...@estima.com> wrote: > > > > OS Version: Mac OS X 10.12 (16A323) > > I´d suggest you try this on 10.12.1, in case it´s a known problem > that´s fixed. If not, you should probably go ahead and submit a bug > report with the exception message and backtrace. In cases like this, > you´ll often get a "triage" response from Apple within a couple > of days, telling you what additional information they´d like to see. > > If there´s anything rational to be concluded from the information > you provided, it´s that the 2- and 3-finger swipe is by default a > scroll, so is there any chance that your scroll range (content size > and offset) is excessively large, or messed up in some way that you > can see? > > --- 1560 Sherman Ave #1029 Evanston, IL 60201 USA _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
