Hide Forgot
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!