Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • batsim batsim
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • batsim
  • batsimbatsim
  • Issues
  • #127
Closed
Open
Issue created Aug 25, 2021 by Millian Poquet@mpoquetOwner

Composed tasks may lead to stack overflow

Currently (6eae4b37), composed profiles are executed by a recursive function, which may easily lead to stack overflows is a big number of subtasks is requested. This can easily happen with sequential tasks if one wants to repeat the sequence many times.

Solution: Do not use the call stack to implement this behavior, use a non-recursive function with a stack data structure instead.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking