[10.10] [OS X] Finder extensions spams console system log #3782
Comments
guruz
changed the title
|
Same problem here. |
|
Same problem. Relaunching Finder through Force Quit Applications solved for me. |
|
I would also see this occasionally for other applications before, but I can't see this logging anymore with OS X 10.11.2. |
|
OK I saw it again now, also every 5 seconds, some Finder state might be needed to trigger it. |
|
10.11.2 here and I see it as well here:
|
|
If it comes every 5 seconds, and only when the sync client isn't running, then it can only be this line that causes it: https://github.com/owncloud/client/blob/v2.1.0/shell_integration/MacOSX/common/SyncClientProxy.m#L46 But there isn't much that we do there, the documentation says that it returns null if if couldn't connect and it does, but it seems to output this message in the process of failing. It could have to do with the way that we close the connection on one side or the other, I'm not sure. |
|
Are all of you using Google Drive. I can see that this may be related to that .. will have to read more log messages to be sure. Stopping Google Drive, stopped these messages. |
|
Some Extention is causing it. E.g. Google Drive or in my case odrive.
from http://apple.stackexchange.com/questions/222647/how-to-find-offending-finder-extension Also what helped was simply running odrive (it was off) and the spamming stopped. I even got this notice: FinderSyncExtension[63387]: 💩 odrive Finder Extension loaded 💩 Well, thanks - could not leave it alone, huh? Had to spam the crap out of my log. |
|
FYI in my case Box Sync was causing this. Even while the Box Sync app was not running, nor was its' client icon visible in the Mac bar. Killing the Box Sync Extension within Activity Monitor stopped the log spamming. |
|
I've just noticed that the OwnCloud client v 2.2.2 (build 3472) is spamming the logs with the same message. In my case, I have verified that no other Finder extensions are installed and that it is that of OwnCloud that causes this. In my case, these messages were posted at these intervals: about 20–30 µs, 1 s, and 4 s (in this repeated pattern). I have updated to 2.2.3 (build build 3601) and for the moment, this message does not show up. I will report here if this behaviour happens again. |
|
Well, I've just remembered to check this behaviour with the newest OwnCloud client v 2.2.4 (build 3709), and there is the same error message, but now always coming exactly every 5 seconds. Quitting the OwnCloud client or restarting Finder does not make any difference. Killing ownCloud Extensions process in various combination does not stop the error message either (I meant to say killing it before restarting the client). |
|
killing box sync seems to get rid of the messages |
|
Still happening with 2.3.1 :[ |
|
I don't think this is our bug, we could probably avoid it by not using an NSConnection, or by trying to tweak its usage, but this otherwise looks like a macOS bug triggered by the way we use it. Other extensions also produce the same messages: http://apple.stackexchange.com/questions/222647/how-to-find-offending-finder-extension |
|
As far as I can tell this is not an issue with the Nextcloud/Owncloud client. I am experiencing this same issue at 2 second intervals on OS X Yosemite (10.10.5).
Uninstalling the Nextcloud client had no effect on the messages. Uninstalling Box Sync seems to have fixed the issue entirely. |
|
Lately, I did not have these pesky error messages (Yosemite 10.10.5 and NextCloud client v 2.3.0rc1), but when I had them with the client version 2.2.4, it was definitely not because of Box Sync because I never had it on any of my computers. |
Note the 5 sec pauses
The text was updated successfully, but these errors were encountered: