Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1367614 - curl_multi_wait gets stuck in a loop in DotNet Core application
Summary: curl_multi_wait gets stuck in a loop in DotNet Core application
Status: CLOSED DUPLICATE of bug 1347904
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: curl
Version: 7.4
Hardware: x86_64
OS: Linux
Target Milestone: rc
: ---
Assignee: Kamil Dudka
QA Contact: BaseOS QE Security Team
Depends On:
TreeView+ depends on / blocked
Reported: 2016-08-17 02:08 UTC by Steven Haigh
Modified: 2016-08-17 14:52 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2016-08-17 07:40:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Steven Haigh 2016-08-17 02:08:50 UTC
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:

A possible fix was identified in libcurl 7.32.0. The commit reference is:

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.

Comment 2 Kamil Dudka 2016-08-17 07:40:01 UTC
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 ***

Comment 4 Kamil Dudka 2016-08-17 14:52:19 UTC
(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!

Note You need to log in before you can comment on or make changes to this bug.