maliput / maliput/delphyne

Avoid deadlock on simulation runner shutdown with python binding

Open
#168 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

type: bug
Dominant language
C++
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

As documented here there is a possible deadlock situation when shutting down the simulation runner from python. One possible solution would be to use a timed mutex as described here. Another approach with timed mutexes would be to implement the busy waiting loop on the python side.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Read PR 162's linked diff and discussion first to identify the simulation runner shutdown path and Python binding entry point. Reproduce the shutdown scenario from Python, then evaluate the timed-mutex and Python busy-wait approaches described in the issue; done means the runner shuts down without deadlocking.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, python
Domain
autonomous-driving
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.