eclipse-score / eclipse-score/kyron

[Kyron] Creation of Timer consumes lot of stack even though its on heap

Open
#5 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
2
Forks
12
Avg merge
21h 55m
Merged PRs (30d)
4

Description

In `/src/async_runtime/src/time/mod.rs`, if MAX_TIMERS is defined as (1024 * 16) or more, then it results in a segmentation fault when Timer is created on the QNX target. It is due to more stack consumption than the default allocation on the QNX target.

DoD:
- Make sure TimeWheel does not need to use an intermediate stack variable to initialize heap allocated one

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.