RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
alsaloop uses 100% CPU when playing HTML5 video in Firefox.

Version-Release number of selected component (if applicable):
alsa-utils-1.0.22-5.el6.x86_64
alsa-lib-1.0.22-3.el6.x86_64
kernel-2.6.32-474.el6.x86_64

How reproducible:
always

Steps to Reproduce:
Execute test case: https://tcms.engineering.redhat.com/case/165694/?from_plan=6110
play https://www.youtube.com/watch?v=C2ODfuMMyss

Actual results:
alsaloop starts using 100% CPU after a while

Tested on a few different systems using RHEL-6.8-20160330.0. After successfully setting up alsaloop using alsa-delay I started up top in order to monitor CPU usage and then loaded up an HTML5 video on Youtube. Within anywhere from 5 seconds to 90 seconds I saw alsaloop hit 100% CPU usage. Reproduced after multiple reboots of each machine as well.

Fix:

http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;
h=e61f35ba4dd1bb0802320d25ecbc8a31ed85caea

Tested using RHEL-6.9-20161128.n.0 (i386 and x86_64 Workstation) on a system and tried the test from the summary. I have not seen the CPU usage for alsaloop go above 6% during any of the tests whereas when testing against 6.8 I would see the CPU usage hit 100% within a few minutes. Marking as verified.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0714.html