Path3D Crash in busy scene
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by reproducing the crash in a busy scene on Windows 11 using the tested Redot versions. Compare adding a Path3D child CSGPolygon with clicking the toolbar's add-point button, including behavior after restarting Redot and in a new project; done means both interactions remain stable without an application crash.
Written by the indexing model from the issue text.
Description
Tested versions
Latest versions tested Redot 26.3 BETA 1 and previous versions
System information
Windows 11 Home x86 64 Intel Core i5 14400F 16.0GB Dual-Channel RAM @ 2793MHz Nvidia 5060GTX
Issue description
This is an odd bug I've noticed for a while now. It is an application crash that occurs when the Path3D is used. I have not been able to reproduce it within new projects, as it appears to only occur in scenes with a lot going on i.e. many nodes present.
Steps to reproduce
The crash is pretty consistent in busy scenes. It Occurs after adding the Path3D node to the scene tree, then either adding a CSGpolgon to the path3d node as a child node, or clicking the add point button on the toolbar. Redot hangs for a moment then crashes without warning.
Upon restarting Redot, the CSGpolygon can be added, or the 'add point' button can be interacted with, without any crash. This remains stable until a new scene is created and the same crash occurs again.
Minimal reproduction project (MRP)
I have had no luck reproducing this is within new projects. Appears to only happen in busy scenes.
- Dominant language
- C++
- Stars
- 6.1k
- Forks
- 337
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 35
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from Redot-Engine/redot-engine
-
Write after free upon adding WorldScape3D to scenePossibly taken @OldDev78 claimed this today. Openbug confirmed high priority release blocker topic:worldscape usability
Redot-Engine/redot-engine#1523 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
bug known problem usability
Difficulty 3/5 1-2 days Newbie friendliness 62/100
Redot-Engine/redot-engine#1519 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 Half a day Newbie friendliness 52/100
Redot-Engine/redot-engine#1516 ·
Maintainers usually reply within 1 day
-
bug needs testing usability
Difficulty 5/5 Over a week Newbie friendliness 20/100
Redot-Engine/redot-engine#1514 · 4 comments ·
Maintainers usually reply within 1 day
-
bug confirmed topic:gdscript usability
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Redot-Engine/redot-engine#1482 ·
Maintainers usually reply within 1 day
All issues in Redot-Engine/redot-engine
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Mac mini M6 (16 GB): Q2_0 streaming works - measured 11.7->27.2 tok/s + arena fix for sub-32 GB MacsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
champion good first issue remake source/qq
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
metasequoiaime/msime-windows#1025 ·
Maintainers usually reply within 1 day
-
backlog bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
EchoTools/nevr-runtime#653 ·
Maintainers usually reply within 1 day
-
`--fail-require-skip` never fires: run_tests.py searches stdout, but the unittest binary writes the skip summary to stderrPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day