On May 22, 2016, at 12:48 PM, Seth Willits wrote:
>
> I'm thoroughly confused and increasingly desperate. *All* of the threads in
> my application periodically are blocked for 30-50 ms pretty regularly, about
> every 150 ms.
Whenever I read about symptoms like this, I
On May 22, 2016, at 10:48 , Seth Willits wrote:
>
> Can anyone think of what I should look for to figure out *why* they're
> blocked?
Do these operations go on long enough that you can see the usage stabilize in
Activity Monitor? If so, what are the user and system
OS X. It happens in all circumstances.
--
Seth Willits
> On May 22, 2016, at 10:59 AM, Alex Zavatone wrote:
>
> Mac, iOS? If iOS, device or sim? IPad?
>
> Try publishing and not running through Xcode.
>
> Sent from my iPhone
>
>> On May 22, 2016, at 12:48 PM, Seth Willits
Mac, iOS? If iOS, device or sim? IPad?
Try publishing and not running through Xcode.
Sent from my iPhone
> On May 22, 2016, at 12:48 PM, Seth Willits wrote:
>
> I'm thoroughly confused and increasingly desperate. *All* of the threads in
> my application periodically are
I'm thoroughly confused and increasingly desperate. *All* of the threads in my
application periodically are blocked for 30-50 ms pretty regularly, about every
150 ms.
I'm processing a bunch of data via NSOperations running in a couple of "serial"
(maxConcurrentOperationCount = 1)
> On 2016 May 22, at 02:25, Bill Cheeseman wrote:
> I am using NSplitViewController in a Mac application with a storyboard, and I
> think it's working well. I had tried it with a nib-based version of my
> application first, without success despite a lot of time put into
Hallo All,
I have a view-based OutlineView with one column bound to an TreeController
(arrangedObjects) and the TableViewCell bound to objectValue.name. The
TreeController is bound to the managedObjectContext.
Nearly everything is fine. With the Add-Button a new line will be added with
the
> On May 22, 2016, at 1:34 AM, Jerry Krinock wrote:
>
> Ten years ago, I think the community opinion was to eschew NSSplitView in
> favor of non-Apple alternatives such as RBSplitView, because of its bugs and
> weirdness. Recently, I thought I’d read somewhere that
> On May 20, 2016, at 11:55 PM, Graham Cox wrote:
>
> The view is definitely being marked dirty, and I’m explicitly calling
> -displayIfNeeded, and -drawRect: is getting called as a result. But the
> screen is not updated. I tried making an explicit call to flush the