Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
inko
inko
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Inko
  • inkoinko
  • Issues
  • #186

Closed
Open
Opened Nov 28, 2019 by Yorick Peterse@yorickpeterseOwner

Acquire the mailbox lock when cleaning up a process after termination

When a process terminates, we finalise all of its blocks and send them back to the global allocator. If another process sends a message to it in the mean time, we may end up corrupting memory.

In addition, we should not send a message to a process that has just terminated itself. Messages sent to a terminated process will never be received, meaning their memory is not released until the last reference to the process is gone. We can probably mark a process as suspended by tagging a bit in the suspended attribute.

Assignee
Assign to
Backlog
Milestone
Backlog
Assign milestone
Time tracking
None
Due date
None
Reference: inko-lang/inko#186