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:
When running a C# program that waits for events, the DotNet core application waits for input while the underlying libcurl event gets stuck in a loop.

This causes the application to use 100% cpu usage.

Affected Components:
libcurl.x86_64 7.29.0-25.sl7

This has been reported to the dotnet core github Issues:
    https://github.com/dotnet/corefx/issues/9751

A possible fix was identified in libcurl 7.32.0. The commit reference is:
    https://github.com/curl/curl/commit/6d30f8ebed34e7276c2a59ee20d466bff17fee56

This issue does not occur to distributions using libcurl versions 7.32.0 or beyond.

I'm not sure exactly what the official policy is for backport requests - or if this is the only commit required to fix this issue with DotNet Core vs libcurl - however am willing to test packages in our environment to verify / validate any fixes.

Thank you for reporting the bug!  This is going to be fixed in RHEL-7.4.  See bug #1347904 for details.

*** This bug has been marked as a duplicate of bug 1347904 ***

(In reply to Kamil Dudka from comment #2)
> This is going to be fixed in RHEL-7.4.

Sorry, I meant RHEL-7.3.  Thanks to Ken Dreyer for making me aware of the typo!