Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Spotifree generates several system.log messages per second in Yosemite #32

Closed
swrobel opened this issue Aug 20, 2014 · 12 comments
Closed

Comments

@swrobel
Copy link

swrobel commented Aug 20, 2014

Running Yosemite DP6 and seeing my system logs filled with this exact message as long as Spotifree is open and Spotify is playing a song:

8/20/14 4:03:42.271 PM Spotifree[1087]: AppleEvents: Send port for process has no send right, port=( port:28651/0x6feb rcv:1,send:0,d:0 limit:5) (findOrCreate()/AEMachUtils.cp #526) com.apple.main-thread

I realize Yosemite is pre-release, but just wanted to give a heads-up on the potential issue.

@artemgordinskiy
Copy link
Owner

Thanks! I hope we will fix this before the release :)

@artemgordinskiy
Copy link
Owner

Do you happen to know how could this issue be fixed? Google is not particularly helpful with this one :)

@swrobel
Copy link
Author

swrobel commented Sep 19, 2014

I don't, sorry. I just checked in DP8 and this is still occurring. It isn't a huge deal as Spotifree still seems to block ads.

@lrzuniga
Copy link

This still seems to be a problem:

2014-10-31 2:25:30.794 PM Spotifree[3722]: AppleEvents: Send port for process has no send right, port=( port:31179/0x79cb rcv:1,send:0,d:0 limit:5) (findOrCreate()/AEMachUtils.cp #526) com.apple.main-thread

@artemgordinskiy
Copy link
Owner

Thanks to an educated guess, identified the exact lines causing this issue (from the isAnAd method):

NSInteger currentTrackNumber = self.spotify.currentTrack.trackNumber;
NSString * currentTrackUrl = self.spotify.currentTrack.spotifyUrl;

Still no idea why accessing Spotify's "currentTrack" objects and its properties would cause such warnings in the log though.

@mastershadow
Copy link

Issue is still present.

@JrCs
Copy link

JrCs commented Jan 4, 2015

There seem to be a problem with ScriptingBridge in Yosemite. A lot of applications that use ScriptingBridge have the same issues.

@enellis enellis added the wontfix label Mar 8, 2015
@enellis
Copy link
Collaborator

enellis commented Mar 8, 2015

Apple... Please do your work. Impossible for us to fix.

@pmiddlet72
Copy link

Happening in 1.6.3. Not sure how much of a resource this actually takes up. Essentially it's telling me that the port it wishes to send on (10523/0x291b in this case) doesn't have permissions for sends. Which reminds me, here's a little relevant gem

@vachooho
Copy link

I have similar warning logged each time I do send AS event using ScriptingBridge- in my case there is no impact on functionality - only excessive logging. I reported this to Apple some time ago, and today I got in my bug report "fixed in OS X 10.11". No explanation for the fix and no indication if it would be fixed in 10.10 - and I don't see that message logged in El Capitano preview.

@artemgordinskiy
Copy link
Owner

@vachooho Thanks for letting us know! Glad to hear they finally fixed this.

@jdelisle
Copy link

On Yosemite, use the Console's Ignore Sender option on that log message to mitigate the issue. Keeps your logs clean :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants