Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • G GLib
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 859
    • Issues 859
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 42
    • Merge requests 42
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • GLib
  • Issues
  • #2326
Closed
Open
Issue created Feb 12, 2021 by Valentin David@valentindavidDeveloper

g_slice_alloc hangs on child process on fork

When a fork is called other threads are doing memory allocations, g_slice might have a mutex locked at that point. So any new allocation in the child process of the fork, then will hang in g_slice_alloc.

G_SLICE=always-malloc does not suffer of the issue.

Here is an example of program that would hang.

If it does not reproduces, try increasing THREAD_N and/or ALLOC_N.

Assignee
Assign to
Time tracking