In case anyone else comes across this:

I finally managed to track down the trigger for this issue. I have some sibling 
views, one which is along the top of my window. In some circumstances when I 
switch into full screen mode, I set the height of this view to zero and 
expanded the other main view to fill the screen.

If I change the size of the document view in my scroll view (the main view 
which I have now expanded to fill the screen), and then use scrollPoint, it 
must trigger some sort of caching operation for the window. At that point, it 
chokes on the zero height view at the top of the window. Don’t ask me why - as 
far as I can tell this does not happen if the zero height view is at the bottom 
or on either side with zero width.

Setting the height of the view to 1 did not fix the issue, but setting it to 2 
did.

It was choking on argb32_image_mark or related methods, so all I can assume is 
that something about the configuration made it unable to create an image (there 
used to be a similar issue apparently in iOS up to 7.1.2.

I have now managed to work around the problem, but this is clearly new behavior 
in 10.10, seems totally bizarre, and is not triggered by swipe scrolling or 
pinch zooming.

Thanks again for the suggestions of places to look.

Gideon


> On 18 Nov 2014, at 7:53 am, Graham Cox <[email protected]> wrote:
> 
> ...
> 
> 
>> On 18 Nov 2014, at 12:58 am, Gideon King <[email protected]> wrote:
>> 
>> I have always done this using scrollPoint on my view. I have been using this 
>> since 10.6. My view is not layer backed and has a single subview which is a 
>> layer *hosting* view.
>> 
>> Now in Yosemite 10.10, this takes a *very* long time at 100% CPU, with a 
>> stack trace looking something like this:
>> 
>> CoreGraphics`argb32_sample_argb32 + 621
>> CoreGraphics`argb32_image_mark + 1696
>> CoreGraphics`RGBA32_image + 1156
> 


_______________________________________________

Cocoa-dev mailing list ([email protected])

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 [email protected]

Reply via email to