SIGPROF keeps a large task from ever completing a fork()

Solution In Progress - Updated -

Issue

  • A process with a large amount of allocated memory pages may enter an infinite loop, due to restarting the clone syscall, when receiving SIGPROF during fork.

Environment

  • Red Hat Enterprise Linux (RHEL) 6
  • Red Hat Enterprise Linux (RHEL) 7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.