Ticket #169 (closed defect: lackofresponse)

Opened 4 years ago

Last modified 11 months ago

rtp: extremely high CPU load and delays

Reported by: Rudd-O Owned by: mkbosmans
Milestone: Component: daemon
Keywords: Cc:

Description

I'm using PA 0.9.8 and RTP to cast to another machine with a PA server, and alsa emulation. On the source machine, using amarok with either the pulseaudio or the alsa output plugins becomes impossible (the audio stutters uncontrollably) when a Flash app starts playing any audio. During all this, both amarok and pulse saturate my both cores in user CPU%. Actually, even when only using amarok (and artsd is also loaded), pulse consumes a hefty dose of CPU, and so does amarok.

I'm running PA manually upon login because PA refuses to autostart as well (tried the client.conf setting, to no avail, and strace gave me nothing useful except that pulse actually loads but dies when reading from a socket I think?).

Relevant files attached.

Attachments

default.pa (3.8 kB) - added by Rudd-O 4 years ago.
client.conf (1.4 kB) - added by Rudd-O 4 years ago.
daemon.conf (3.8 kB) - added by Rudd-O 4 years ago.
asound.conf (64 bytes) - added by Rudd-O 4 years ago.

Change History

Changed 4 years ago by Rudd-O

Changed 4 years ago by Rudd-O

Changed 4 years ago by Rudd-O

Changed 4 years ago by Rudd-O

Changed 4 years ago by Rudd-O

I should mention that when I cast directly (NOT through a tunnel, but selecting the machine) using padevchooser, everything works smoothly. Of course, I wanted to cast over RTP by default because my house has several locations where I want to hear music.

Changed 3 years ago by lennart

  • summary changed from extremely high CPU load and delays to remote access: extremely high CPU load and delays

Changed 11 months ago by mkbosmans

  • owner changed from lennart to mkbosmans
  • summary changed from remote access: extremely high CPU load and delays to rtp: extremely high CPU load and delays

Does the problem still occur in a recent version of pulse?

Changed 11 months ago by mkbosmans

  • status changed from new to closed
  • resolution set to lackofresponse

Closing now, because it is probably fixed now.

If the problem persists in a recent version of pulse, please reopen.

Note: See TracTickets for help on using tickets.