LM/HM: heap allocations after initialization

Open
  • Is something wrong?
#952 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp, rust
Domain
backend

Research direction

Start with the dependency AoU triage in docs/module/safety_mgt/dependency_aou_handling.rst, then inspect the cited allocation sites: health_monitor/src/rust/deadline/ffi.rs:22-34, protected_memory.rs:17, and the Launch Manager runtime uses of std::vector and std::string. The issue requires a maintainer decision to remove these allocations or justify a deviation in the Lifecycle safety concept; done means recording the verdict in the triage page and closing the issue.

Written by the indexing model from the issue text.

Description

AoU aou_req__platform__no_heap_alloc_after_init (Avoidance of heap allocations after initialization) of a dependency of Lifecycle is open in the dependency AoU triage (#923, docs/module/safety_mgt/dependency_aou_handling.rst).

Component: Launch Manager, Health Monitor

Evidence: HM allocates at runtime: health_monitor/src/rust/deadline/ffi.rs:22-34 ("For now, Deadlines are kept allocated on heap individually", TODO memory pool); protected_memory.rs:17 TODO. LM uses std::vector/std::string at runtime; FixedSizeVector only in alive_monitor.

Decision needed: 'should' AoU: maintainer must either remove runtime allocations (memory pool for HM deadlines, LM state machine) or justify the deviation in the Lifecycle safety concept.

Once decided, the verdict in the triage page is updated (fulfils link, forwarded AoU, or a documented deviation) and this issue is closed.

Dominant language
C++
Stars
7
Forks
37
Avg merge
2d 9h
Merged PRs (30d)
117

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-score/lifecycle

All issues in eclipse-score/lifecycle

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.