Bug 1367614
| Summary: | curl_multi_wait gets stuck in a loop in DotNet Core application | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Steven Haigh <netwiz> |
| Component: | curl | Assignee: | Kamil Dudka <kdudka> |
| Status: | CLOSED DUPLICATE | QA Contact: | BaseOS QE Security Team <qe-baseos-security> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.4 | CC: | kdreyer, kdudka |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-08-17 07:40:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
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! |
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.