Skip to content

GitLab

  • Menu
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 889
    • Issues 889
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 49
    • Merge requests 49
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & 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
  • GNOME
  • GLib
  • Issues
  • #449

Closed
Open
Created Sep 13, 2011 by Bugzilla@bugzilla-migration💬Reporter

make fork()ing GMainContext explode sooner

Submitted by Allison (desrt)

Link to original bug (#658999)

Description

trying to have a GMainContext across a fork() is a recipe for intense amounts of pain. first: the worker thread doesn't follow you. second: you're now sharing an eventfd with your parent.

sometimes you can kind of get away with it and end up with weird bugs that are difficult to track down. we should make a point of asserting quite rapidly if we detect this situation.

Assignee
Assign to
Time tracking