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, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content