November 2018 - Cocoa-dev - lists.apple.com

Re: Quick sanity check for iOS AVAudioSession
by Quincey Morris 29 Nov '18

29 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=teal.net; s=teal; h=references:to:cc:in-reply-to:date:subject:mime-version:content-type: message-id:from:from; bh=sTiSFaHXcXs9ezOCuA9hOSk7BsyGoAI3DBOgjXML9yM=; b=NDXzxLWn2w3n8YQAfYZLEr3aGzuh+pO6etIzN26EqyYmPaOSAsR8I7ZBDshOrSM6Xj1pSjKbzwjBT jQ24gtrSm1ZRe0oqQi6VQgKNeJH40YyLlCrBh8KjaXvO1iLzUyP3yI0WoT8lx1DjS0XSdzDrb16uJb dg9qktcGoPnfYLcs= That all looks correct to me. > On Nov 29, 2018, at 06:22 , Eric E. Dolecki <edolecki(a)gmail.com> wrote: > > Does this seem about right? _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Quick sanity check for iOS AVAudioSession
by Eric E. Dolecki 29 Nov '18

29 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=G7R1WqWaSIwQ2Tw0Wu8AQ2u92WCBzwjnk4+t0LZ2Kt0=; b=Zib1zERS8QWFw6xEH48ErddCb9AB6pvWcYVcKvXYGTQWAarjaGRVDUW7G1hWBKT+G2 9T+zGtyITJylOEhaWhOJ3MQbU9hCwzMsoBd/jJtHAJA0Sl1AeELDOr5ubys1F+XU+1zY xwwJXf34g8Gbl6mp19CjLo5eco+i62p/2PfIDh8YRmEDdpa9Zt2gVAD+PFmRLp6eaUjX yb6ps3nB+9GlKq/Q9F3jUJbGyUYpENkeHAbo/TNVE/ZS6jg+svTJYeGzIn/Sej5AtO7c nqYFMRaKCVoglvLaX98M9if+/qdtCj9dpCpM+EuBubU5NL5jRTO+kL+h4xEic3yuyDVk MqWw== Hey all, I have an application I am developing and I cannot currently build to a device. So I am asking in lieu of proper testing on my end at the moment. 1. I would like to mix my audio with that in another session (say Apple Music is playing something). So before I play my app audio, I call this: func activateAudioSession() { let session = AVAudioSession.sharedInstance() do { try session.setCategory(AVAudioSessionCategoryPlayback , with: [. duckOthers, .allowBluetoothA2DP]) try session.setActive(true) } catch { print("Activate session error: \(error)") } } When my audio has completed playing, I call this (in all cases): func deactivateAudioSession() { let session = AVAudioSession.sharedInstance() // Do this on a separate thread because on UI thread causes 500ms delay. This unducks others after being ducked. DispatchQueue.global().async { do { try session.setActive(false) } catch { print("Deactivate session error: \(error)") } } } 2. There might be a time when I want to stomp on any audio from another session. In that case, I have another method I call that does NOT contain the .duckOthers option which I take to mean that mix with others is not enabled. func activateAudioSessionWithStompingOthers() { let session = AVAudioSession.sharedInstance() do { try session.setCategory(AVAudioSessionCategoryPlayback , with: [. allowBluetoothA2DP]) try session.setActive(true) } catch { print("Activate session error: \(error)") } } Does this seem about right? Also - if I stomp on another session (again, say Apple Music), that session pauses. Once that's done the user would need to manually unpause it - there is nothing I can do programmatically to get that going again, correct? Thanks for your attention, Eric _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

viewDidLoad is OK, IOReturn isn't
by Casey McDermott 29 Nov '18

29 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1543463416; bh=BwDj3mB70YC3+BpXcsMNoEEkLaC/an+N21qBuHMRAh8=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=C5mQS39g/tXwpLDdRFFtxJ+quogAyeV64OJugK/KYiyxSi0RIVZgs1yUcsEnhywdUN5mAaIbQJTYuPQCrfKIhwJEktX8qHC5BHsRX6a5XBgOrMXR0irauhy8rWogNRGGg4EsUBGKI0IfG1Rh7LDljMtrp9ll1cQjmWjO5u30Pf2gfqWQ6a6qkjWkqYVMZbLRq3cxmOWurYpKP6Si72okFIzU9cM6WauucYBHyyogKvSKq+u7a8Inp092ty6Yvv/dlL9KqcXNdPGu1hxPA9gqhX32DYXhvi3soZId/BmVfyWzqoY7C1zcpbz7edofk0wR3c4ZHvW2PeiMc4k1kaxatA== Sorry, switching from macOS to macOS 10.12 as a base SDK fixed the compiler errors in NSViewController and elsewhere. It builds OK with that SDK. However using the 10.13 SDK gives a preprocessor error for IOKit/IOReturn.h file not found, at #import <CoreServices/CoreServices.h> This is on a recently installed 10.13.6 machine and Xcode 10.1. There are fixes on Stack Overflow but for older versions. Looks like the frameworks have changed since then. Thanks, Casey McDermott TurtleSoft.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

viewDidLoad
by Casey McDermott 29 Nov '18

29 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1543462134; bh=bGrj7mQzzFRstrQpZJ7cksrb5pFce5iFNVK9xH8JwMU=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=IyHkjAfotaoSQOZAQ6dG4B3IiBaIMooKP7090DHYyAXMKxrkvWr+e/Qx9ghk6RP5EFMXQ6UC2DeV8duzVYE/JT9HQL80QTnDaia2Lj8lSATUNwQWB1Q45ALxZcC2VRVI+JlI6krZS9DAcw0qMSI0CktnjG7IlhAm09yYIGbHZqeb/qXtemw/cLwyf8RNNNkq66ijaIGxKb+ydwAfwzPjTks2pWeTw5RbQtnSWZKUEq3jQPlT9MdzJS7UEPhJefDzo4/Htvk7UneRxy9CX8meVVcnyVCyYuPaJtNhJZQQ6x4qTJhcP9EDmUH5ll3XuF/okil4CAREWF17RvyisbW9ZA== We override viewDidLoad in a few view controller classes, and call [super viewDidLoad]; in them. Recompiling from OS 10.11 to OS 10.13 with a 10.13 deployment target gives a new error: "No visible @interface for 'NSViewController' declares the selector 'viewDidLoad'" Apples online docs don't say anything about it being deprecated. Is it no longer OK to call it? It's still in the header file. NSViewController is the primary suspect for the crashing problems we experience after the move. Thanks, Casey McDermott TurtleSoft.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Diagnosing memory problems
by Steve Mills 28 Nov '18

28 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1543383751; bh=5XFjKdi14bgi/88VQXOyJ05D34HwT0b1vtX3Vu2k8xM=; h=From:Content-Type:Mime-Version:Subject:Date:To:Message-Id; b=Uz/cSbPlqEP7VMPnjvBnOaOJKYn0rGRKfdwCOdmosekxCEk+PRShPP7vb2L747tHc nN32wabILfPgtK1esru3vYJB7eN72/KvaavKWtqEO85lztoj8iC4clUoJP4HqEQfgZ iPsFOOYXrGgc6SWQlA3fEtqPN0qvW/6DoIO2P9TxDdqa+Y60YQM+8quOfl4H6QLOkD xIp6gj8AbSxZMBCjPsWSGzhPXWeUA297JWMqsuX7EBBvAe7fXOsKUKWRs8PiGXYUQf bb2KD+OwN5XytyZuODnxgWx+8VjCOQRPzK1O5f9UyCPmDwsAS3dWCE/7hPm9r7HLbi 154L20oZ+SYhw== > On Nov 27, 2018, at 16:56, Casey McDermott <support(a)turtlesoft.com> wrote: > > Our main window has a tool bar across the top, an outline view on the left, > and a tab view on the right. Choosing an item from the outline view fills a > data entry screen into a new tab on the right. > > We started out using OS 10.11, but just switched to newer OS versions. 10.12 > has a couple display quirks but runs OK. In 10.13 and newer, switching tabs > often crashes. It gives a warning about releasing a data entry field that is > already released. > > In C++, we would diagnose this with a breakpoint in the destructor and then > check the stack trace. But with ARC, a breakpoint at dealloc just shows > performDelayedCleanup and then main. No clues to what's wrong. Is the data on the right displayed via bindings? That can easily bite you if things aren’t worked out the right way. Is the “data entry field” loaded separately from a nib, and is the controller or owner actually owned by anything? Thanks also a common mistake. It’s common to strong assign the controller to the window, doc, or app delegate, whichever thing actually instantiated it, so it will own it for its lifetime. -- Steve Mills Drummer, Mac geek _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Diagnosing memory problems
by Sean McBride 28 Nov '18

28 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Organization: Rogue Research Inc. On Tue, 27 Nov 2018 16:53:26 -0700, Rob Petrovec said: >Actually, you want the Zombies tool. That finds overreleased objects >like ones that cause the spew you are seeing. See also: 1) man guardmalloc 2) <https://clang.llvm.org/docs/AddressSanitizer.html> 3) NSZombieEnabled 4) CFZombieLevel Cheers, Sean _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Diagnosing memory problems
by Rob Petrovec 27 Nov '18

27 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1543362809; bh=T+BimeWXq5buYIq7wjjbw0gWwZj9g0pjrFgPkU54KRM=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=lNkIW2CbRr1ijIyqW8Pqak3+YQkm/P03jXOtmUHfe3zJPzIEFG+ZRwHe3/SfE9AVK GPPF01z9anrEPxKuW1kAvhkVKFcMV4DXImLN6nI9bKI8oPXWfxjBA3BSPLJ10r7l89 Ao3ERG3X5Wub5oxUqxuP44UrFmqOTNiJMRWgzj7sIWHXqUPiKd2sz1VWQNoX/Vj3dy /MmHZESy/5ADykViuPBcffoIGtAAkLsXFGGb/0olkAQJACGircEKaCcbstK58ytnmH e+4ruV9wX8u+Q8tIA196VXmfPo9jtG7xNHeuRUtJw5fkyHPxWY1s9/UHoci9phkGEd I0g8V9UG6eaiQ== Actually, you want the Zombies tool. That finds overreleased objects like ones that cause the spew you are seeing. —Rob > On Nov 27, 2018, at 4:52 PM, Rob Petrovec <petrock(a)mac.com> wrote: > > Check out the Leaks tool in Instruments (inside Xcode.app) > > —Rob > > >> On Nov 27, 2018, at 3:56 PM, Casey McDermott <support(a)turtlesoft.com> wrote: >> >> Our main window has a tool bar across the top, an outline view on the left, >> and a tab view on the right. Choosing an item from the outline view fills a >> data entry screen into a new tab on the right. >> >> We started out using OS 10.11, but just switched to newer OS versions. >> 10.12 has a couple display quirks but runs OK. In 10.13 and newer, >> switching tabs often crashes. It gives a warning about releasing a data >> entry field that is already released. >> >> In C++, we would diagnose this with a breakpoint in the destructor and then >> check the stack trace. But with ARC, a breakpoint at dealloc just shows >> performDelayedCleanup and then main. No clues to what's wrong. >> >> Is there lore or are there tools for tracking object lifetimes in Obj-C/ARC? >> >> Anything that changed in 10.13 that might be biting us? >> >> Thanks, >> >> Casey McDermott >> TurtleSoft.com >> _______________________________________________ >> >> Cocoa-dev mailing list (Cocoa-dev(a)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/petrock%40mac.com >> >> This email sent to petrock(a)mac.com > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev(a)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/petrock%40mac.com > > This email sent to petrock(a)mac.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Diagnosing memory problems
by Rob Petrovec 27 Nov '18

27 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1543362765; bh=HEFU7saqw3ufjsrfoPa8Cd8Yn7rtbkNQLYDqPGcAYsw=; h=Content-type:MIME-version:Subject:From:Date:Message-id:To; b=LYnUejAy1B8qN0ysFm+IL++i+8qmw+wwnvLfnAd9xXxJ1bHfAym+cx4bmzYKiIK/R 3hU8TrA24tkMwqDm0Dele/EuJku0C2iJtqNRKo3uYbs3LvUSrV5377clWdqolb/FI2 vdqlK0Li8u64LHXM9/1YNFSuUxPmy1BkPrJmtm09qwVu6W4lZjDgrdaA0uo+vdDga2 k6Zs82GteAupMXx2Z4zRMXV3rvyTcwnLJKtwqaNWIUC9WJDxRTqaiPh5EGeHF/QUwR yaTVQPblGN/6T6OPqLrsX1jnit1296Toq4XlOH4mjgFI1siu757JNAWMX4h9ngOYVM btPw6z2GYNEog== Check out the Leaks tool in Instruments (inside Xcode.app) —Rob > On Nov 27, 2018, at 3:56 PM, Casey McDermott <support(a)turtlesoft.com> wrote: > > Our main window has a tool bar across the top, an outline view on the left, > and a tab view on the right. Choosing an item from the outline view fills a > data entry screen into a new tab on the right. > > We started out using OS 10.11, but just switched to newer OS versions. 10.12 > has a couple display quirks but runs OK. In 10.13 and newer, switching tabs > often crashes. It gives a warning about releasing a data entry field that is > already released. > > In C++, we would diagnose this with a breakpoint in the destructor and then > check the stack trace. But with ARC, a breakpoint at dealloc just shows > performDelayedCleanup and then main. No clues to what's wrong. > > Is there lore or are there tools for tracking object lifetimes in Obj-C/ARC? > > Anything that changed in 10.13 that might be biting us? > > Thanks, > > Casey McDermott > TurtleSoft.com > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev(a)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/petrock%40mac.com > > This email sent to petrock(a)mac.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Diagnosing memory problems
by Casey McDermott 27 Nov '18

27 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1543359369; bh=ozxKwfrYJJFUWi6fYm8iuYcwwJW5836dsW3caVypBNs=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=Ihgn8TmHKnRZvqPKh3sxHX6YbFuw4KlK6R3f4S5Iv0V4MufFBbulf5uNinCWx57JFcahdqjbEqAqiEDM+NoN7HCwogagwNNtjtSbfiTL8lQqY+ZRjjET6rAGLhf8GRCY9qenWrRh+Lol4A7RDuj7z5qAgXrL7lObNTMuCq3HmNyzaIYtub29ETp8at2c3pqDj/QoicSsHA8Q4sVAWOv+gaEHlFuAqXedVxzmDPYNl3lNtzUa3lYlyZ2YWDumX3zRmp/NfTTKvgz5XnjfGP9lL8O66OLxQwWJhTGKXX3UE+cQLZb3XoKPBmyLViGNIVJKsjjqpdGgC+R7dwW0uEyx+A== Our main window has a tool bar across the top, an outline view on the left, and a tab view on the right. Choosing an item from the outline view fills a data entry screen into a new tab on the right. We started out using OS 10.11, but just switched to newer OS versions. 10.12 has a couple display quirks but runs OK. In 10.13 and newer, switching tabs often crashes. It gives a warning about releasing a data entry field that is already released. In C++, we would diagnose this with a breakpoint in the destructor and then check the stack trace. But with ARC, a breakpoint at dealloc just shows performDelayedCleanup and then main. No clues to what's wrong. Is there lore or are there tools for tracking object lifetimes in Obj-C/ARC? Anything that changed in 10.13 that might be biting us? Thanks, Casey McDermott TurtleSoft.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Screen saver sometimes starts and stops immediately
by Stephane Sudre 26 Nov '18

26 Nov '18

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=L5xJPQZmYHFbWUmxzDo3+LZGzPaFWceqr3UkmTAPSXY=; b=TCK1N2eWxE5R84UVbmENWU93NB6o1rN4iDm6Rs7hfLYoVgMd9Sw/W6pMVfd4K+wMO2 2g+QFcSXccFyc1PABouoQarZ2TPg0D8jlGthJfxf2f4zO8+Tcy4Kysq4xY5FATm0kzP3 h5Fe5wN0bhYmBrS0A0sdy80BXg+SGhjBN/BzwXtg2Tb9Ju+exQovptjmNZHhJszpeyfQ NShuADFkyPac8jBMtB10aAifMEwt/MJfqhPvpKLKiiHY3ypRNLrp29ZjK5m7GdDptT7m Y3m/0ZAw3L8lLTNSVWU4EZOqdbFA8HYNn7IYWeuTrjetotA7tpFXaJzP0Kmusl1uTk1V ilTg== Could it be that your screen saver is trying to access data in a user folder protected by tccd like ~/Pictures ? info 13:52:14.333614 +0100 ScreenSaverEngine stop animation (id = 0x7ffe73822800) default 13:52:14.334610 +0100 tccd MacOS error: -67050 default 13:52:14.335183 +0100 ScreenSaverEngine -[ScreenSaverEngine startScreenSaver:] -- firstTime 0 info 13:52:14.335516 +0100 ScreenSaverEngine viewWillMoveToWindow was called with NULL window. On Sun, Nov 25, 2018 at 10:37 PM Gabriel Zachmann <zach(a)tu-clausthal.de> wrote: > > I have a problem with my screensaver: it gets started as usual by the OS, > it displays the first image for a second (approx), > and then, sometimes (only sometimes), it gets stopped by the OS. > > I cannot recall anything I might have changed that might cause this behavior > (of course). > Also, I cannot find any hint at a crash or other malfunction of my code. > > > I have uploaded a section of the log -- copied from Console.app -- here: > https://www.dropbox.com/s/gkjys2yww1jz46n/log_screensaver_exit.txt?dl=0 > > (Even though it's just 1 minute of log data , I think it is too lengthy to > include it here. > I did not want to filter it because I was afraid i might loose valuable > information.) > > For instance, at 13:52:13.277129 you can see that my screensaver (ArtSaver) > got started, > and at 13:52:13.465331 you can see the next message from my screensaver that > got logged. > There are some more messages from my code, but nothing unusual, AFAICS. > > At 13:52:18.331654, the screensaver gets stopped, but I don't see any reason. > (And as far as I can remember, I did not stop it at that point.) > > (The only funny thing is that there is a second "startup" message in the log > file at 13:52:14.655737 . > But, IIRC, I have seen that for many years, so I doubt that is the problem.) > > If there is any other info I can provide, or if there is a better way t > provide the information, please let me know. > > Best regards, Gabriel > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev(a)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/dev.iceberg%40gmail.com > > This email sent to dev.iceberg(a)gmail.com -- Packaging Resources - http://s.sudre.free.fr/Packaging.html _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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/site_archiver%40lists.app… This email sent to site_archiver(a)lists.apple.com

1 0