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

HTTP frontend use 100% CPU on OS X #445

Closed
knubie opened this Issue May 7, 2013 · 5 comments

Comments

5 participants
@knubie

knubie commented May 7, 2013

Everything works fine as far as I can tell, just that mopidy uses a constant 100%. Not sure if this is expected behavior or not, but it causes a hot computer and loud fans. Here is a log just in case

** Message: pygobject_register_sinkfunc is deprecated (GstObject)
/usr/local/lib/python2.7/site-packages/gobject/__init__.py:115: Warning: attempting to add an interface (GstImplementsInterface) to class (mopidy+audio+mixers+fake+FakeMixer) after class_init
  type_register(cls, namespace.get('__gtype_name__'))
/usr/local/lib/python2.7/site-packages/gobject/__init__.py:115: Warning: attempting to add an interface (GstMixer) to class (mopidy+audio+mixers+fake+FakeMixer) after class_init
  type_register(cls, namespace.get('__gtype_name__'))
INFO     Starting Mopidy 0.14.1
INFO     Loading config from: builtin defaults, /Users/Matt/.config/mopidy/mopidy.conf, command line options
INFO     Disabled extension mpris: dbus library not found
INFO     Enabled extensions: spotify, mpd, http, stream, scrobbler, local
INFO     Disabled extensions: mpris
INFO     Starting Mopidy audio
INFO     Audio output set to "autoaudiosink"
INFO     Starting Mopidy backends: SpotifyBackend, StreamBackend, LocalBackend
INFO     Mopidy uses SPOTIFY(R) CORE
INFO     Loaded 0 local tracks from /Users/Matt/Music using /Users/Matt/.local/share/mopidy/local/tag_cache
INFO     Loaded 0 local playlists from /Users/Matt/.local/share/mopidy/local/playlists
INFO     Starting Mopidy core
WARNING  Did not find any audio mixers in "autoaudiomixer"
INFO     Starting Mopidy frontends: MpdFrontend, HttpFrontend, ScrobblerFrontend
INFO     MPD server running at [::]:6600
INFO     Using select as epoll is not available
INFO     Connected to Spotify
INFO     HTTP server running at http://127.0.0.1:6680
INFO     Scrobbler connected to Last.fm
@yunzheng

This comment has been minimized.

yunzheng commented May 18, 2013

I have the same issue. I downgraded to 0.13.0 for now:
$ sudo pip install mopidy==0.13.0

@knubie

This comment has been minimized.

knubie commented Jun 5, 2013

Works for me, thanks.

@adamcik

This comment has been minimized.

Member

adamcik commented Jul 9, 2013

Running on 0.14 with -o http/enabled=false should fix this. Problem is likely that ws4py under cherrypy falls back to a select based event loop which isn't well behaved on OS-X. See referenced bugs for more details.

@jodal

This comment has been minimized.

Member

jodal commented Nov 20, 2013

If downgrading to 0.13 solves the issue, it sounds unlikely that ws4py is the culprit.

Do we any other theories? Have anyone tried Mopidy on OS X recently?

@jodal jodal added this to the v0.19 - MPD playlist mgmt and other MPD improvements milestone May 14, 2014

@jodal

This comment has been minimized.

Member

jodal commented May 14, 2014

With the merge of #730 into develop, we've switched the WebSocket implementation from ws4py which used the ineffective select syscall on OS X to using Tornado, which supports kqueue.

I'm closing this issue in the belief that this is now solved. Please open a new issue if you still experience this with Mopidy's develop branch or v0.19 when it is released.

@jodal jodal closed this May 14, 2014

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