Re: Gestures cause crash in Sierra

2016-11-30 Thread Tom Doan 
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  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

Gestures cause crash in Sierra

2016-11-23 Thread Tom Doan 
I'm having a problem with my applications that has come up just 
with Sierra. Any "swiping" gesture with two or three fingers on the 
trackpad causes an immediate crash. (Log below). A four finger 
swipe (if the four fingers are put down very deliberately) behaves 
properly. The fatal thread doesn't include any of my code, so I have 
no idea what's happening. I don't do anything in any of my views to 
handle any of the gestures directly. When I added (for instance) a 
SwipeWithEvent on the view, it never seems to get called. Any help 
with this would be greatly appreciated.

Best regards,

Tom Doan
Estima
---
1560 Sherman Ave #1029
Evanston, IL 60201
USA

Process:   RATSPro [986]
Path:  /Applications/RATS Pro
9.1/RATSPro.app/Contents/MacOS/RATSPro 
Identifier:  
com.estima.rats Version:   9.10.5 (1) Code 
Type:   
X86-64 (Native) Parent Process:    ??? [1] 
Responsible: 
RATSPro [986] User ID:   502

Date/Time: 2016-11-22 11:17:46.241 -0800
OS Version:    Mac OS X 10.12 (16A323)
Report Version:    12
Anonymous UUID:    
7EED464A-4A8E-2079-053C-33A3D31ED801

Sleep/Wake UUID:   
3A646693-9CAC-4B18-A517-C6FAF1D22E3F

Time Awake Since Boot: 6900 seconds

System Integrity Protection: enabled

Crashed Thread:    4  Dispatch queue: NSScreenUpdate

Exception Type:    EXC_CRASH (SIGABRT)
Exception Codes:   0x, 
0x
Exception Note:    EXC_CORPSE_NOTIFY

Application Specific Information:
*** Terminating app due to uncaught exception 
'NSScrolling', reason:
'24332693 bear trap: NSScrollView bad canonicalOrigin 
(NaN) detected!
Please note any info you can in the bug.' terminating with 
uncaught
exception of type NSException abort() called

Application Specific Backtrace 1:
0   CoreFoundation  0x7fff8638a7bb
__exceptionPreprocess + 171 1   
libobjc.A.dylib   
0x7fff9aaf7a2a objc_exception_throw + 48 2   
AppKit  
  0x7fff84212683 
-[_NSScrollingConcurrentSharedData
threadSafePropertyAccess:] + 145 3   
AppKit
0x7fff84214601 
-[_NSScrollingConcurrentEventVBLPreprocessFilter
scrollingVBLMonitor:synchronizeForVBLSerialNumber:times
tamp:updateDuration
:] + 383 4   AppKit  
0x7fff84214414
-[_NSScrollingConcurrentVBLMonitor
_synchronizeForVBLSerialNumber:timestamp:updateDurati
on:] + 535 5   AppKit
 0x7fff8421418d
__42-[_NSScrollingConcurrentVBLMonitor 
resume]_block_invoke + 218 6 
AppKit  0x7fff842140aa
__45-[NSScreen(NSScreenUpdate) 
addUpdateHandler:]_block_invoke_2 + 212 7 
libdispatch.dylib   0x7fff9b39d128
_dispatch_client_callout + 8 8   
libdispatch.dylib 
0x7fff9b3b2c10 _dispatch_continuation_pop + 533 
9   libdispatch.dylib
 0x7fff9b3a8ad2 
_dispatch_source_latch_and_call + 192
10  libdispatch.dylib   0x7fff9b39f966
_dispatch_source_invoke + 1248 11  
libdispatch.dylib 
0x7fff9b3b2a50 _dispatch_continuation_pop + 85 12  
libdispatch.dylib 
    0x7fff9b3a9ea3 
_dispatch_async_redirect_invoke + 734
13  libdispatch.dylib   0x7fff9b39eee0
_dispatch_root_queue_drain + 476 14  
libdispatch.dylib 
0x7fff9b39ecb7 _dispatch_worker_thread3 + 99 15
libsystem_pthread.dylib 0x7fff9b5e9746 
_pthread_wqthread +
1299 16  libsystem_pthread.dylib 
0x7fff9b5e9221
start_wqthread + 13

etc.

(main thread is in the run loop)


___

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