Crash on an Arm board
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 2.2k
- Forks
- 713
- Avg merge
- 9d 12h
- Merged PRs (30d)
- 2
Description
The same code runs fine on an x86 architecture processor but crashes on an arm board. It doesn't crash every time. Usually, it crashes after a few runs. With line-by-line comments, I found that it was the destructuring of Planner that was causing the crash (Informed RRT* and RRTConnect are tested).
Why is it different? What should I do to run it on the arm board?
Memory of the arm board is enough (3G used, 16G total). The cpu is less than half occupied.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the intermittent crash on the Arm board with the reported Planner destructuring, using the Informed RRT* and RRTConnect cases. Compare the Arm and x86 behavior while narrowing the failure around that operation; done means identifying the platform-specific cause and confirming the affected cases run without crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100