Overview
This issue identifies open issues that are likely stale and candidates for closure. Three criteria were used:
- No comments — issue has received zero engagement
- Empty or sparse crash reports — crash report template submitted with missing stack trace or minimal reproduction info
- Reported against Dynamo < 2.16 — these versions are no longer supported and the bugs are unlikely to be reproducible or actionable
Category 1: Issues With Zero Comments
These have received no response or engagement since filing. Many are years old.
| # |
Title |
Filed |
Status |
| #17027 |
Skills in the Dynamo Repo can be improved |
2026-04 |
Open |
| #16276 |
命令: _AeccLaunchDynamo 无法启动 Dynamo (RestSharp assembly error) |
2025-06 |
Closed |
| #15423 |
Dynamo 程序中，只剩下连接线，功能块看不到了 |
2024-08 |
Open |
| #13872 |
Crash report from Dynamo 2.16.1.2727 |
2023-04 |
Open |
| #13846 |
Crash report from Dynamo 2.6.2.15705 |
2023-03 |
Closed |
| #13842 |
Crash report from Dynamo 2.12.1.8246 |
2023-03 |
Closed |
| #11337 |
String of "ConcreteType" being replaced on open |
2020-12 |
Open |
| #10719 |
Override name of the "get" properties inputs |
2020-05 |
Open |
| #10623 |
Incorrect Split of surface by polysurface |
2020-05 |
Open |
| #10482 |
The '+' character (0x2B) cannot be included in a name |
2020-03 |
Open |
| #10167 |
Dynamo Player doesn't work with OneDrive |
2019-11 |
Open |
| #9916 |
Multiplying Point.ByCoordinates() returns null and doesn't throw an exception |
2019-08 |
Open |
| #9236 |
Definitions fail to debug typos/undeclared vars and throw no exception |
2018-11 |
Open |
| #9235 |
Node to code converted to a def: output ports persist, inconsistent state and crash |
2018-11 |
Open |
| #9229 |
Node to code creating recursive dependency |
2018-11 |
Open |
| #7991 |
Error Report 20170621 |
2017-06 |
Open |
Category 2: Empty or Sparse Crash Reports
These use the crash report template but are missing a stack trace, error text, or meaningful reproduction steps. Without this information they cannot be triaged.
| # |
Title |
Problem |
Status |
| #13842 |
Crash report from Dynamo 2.12.1.8246 |
Error referenced in text but not included; no stack trace |
Closed |
| #13872 |
Crash report from Dynamo 2.16.1.2727 |
Stack trace block is empty |
Open |
Category 3: Open Crash Reports Against Dynamo < 2.16
These were filed against unsupported versions. If the bug still exists it should be re-reported against a current version with a fresh stack trace.
| # |
Title |
Version |
Comments |
Status |
| #7991 |
Error Report 20170621 |
1.3.0.875 |
0 |
Open |
| #10436 |
Crash report from Dynamo 2.3.0.5885 |
2.3.0 |
6 |
Open |
| #11084 |
Crash report from Dynamo 2.5.0.7460 |
2.5.0 |
3 |
Closed |
| #11119 |
Crash report from Dynamo 2.3.0.5885 |
2.3.0 |
8 |
Closed |
| #11484 |
Crash report from Dynamo 2.6.1.8786 |
2.6.1 |
6 |
Open |
| #11572 |
Crash report from Dynamo 2.3.0.5885 |
2.3.0 |
1 |
Closed |
| #12132 |
Generative Design Tools - Crash report from Dynamo 2.12.0.5740 |
2.12.0 |
2 |
Open |
| #12266 |
Crash report from Dynamo 2.13.0.3077 |
2.13.0 |
6 |
Open |
| #12603 |
Crash report from Dynamo 2.12.0.5650 |
2.12.0 |
1 |
Open |
| #12639 |
Crash report from Dynamo 2.11.0.4533 |
2.11.0 |
3 |
Open |
| #12656 |
Crash report from Dynamo 2.3.1.11775 |
2.3.1 |
1 |
Open |
| #12662 |
Crash report from Dynamo 2.6.1.8786 |
2.6.1 |
1 |
Open |
| #12663 |
Crash report from Dynamo 2.12.0.5650 |
2.12.0 |
1 |
Open |
| #12714 |
Crash report from Dynamo 2.12.0.5650 |
2.12.0 |
1 |
Open |
| #13311 |
Crash report from Dynamo 2.12.1.8246 |
2.12.1 |
2 |
Closed |
| #13842 |
Crash report from Dynamo 2.12.1.8246 |
2.12.1 |
0 |
Closed |
| #13846 |
Crash report from Dynamo 2.6.2.15705 |
2.6.2 |
0 |
Closed |
| #14494 |
Crash report from Dynamo 2.15.1.6076 |
2.15.1 |
3 |
Closed |
Recommended Actions
- Category 1 (no comments): Close with a "stale" or "needs more info" label. For bug reports, ask the reporter to confirm reproducibility on a current version before closing.
- Category 2 (empty crash reports): Close requesting a new report with a complete stack trace. The crash reporter tool should capture this automatically in newer versions.
- Category 3 (pre-2.16 crashes): Close as "version no longer supported." If the reporter can reproduce on a current version they can file a new issue.
Note: Issues appear in multiple categories where criteria overlap. Snapshotted against open issues as of 2026-04-30.
Overview
This issue identifies open issues that are likely stale and candidates for closure. Three criteria were used:
Category 1: Issues With Zero Comments
These have received no response or engagement since filing. Many are years old.
Category 2: Empty or Sparse Crash Reports
These use the crash report template but are missing a stack trace, error text, or meaningful reproduction steps. Without this information they cannot be triaged.
Category 3: Open Crash Reports Against Dynamo < 2.16
These were filed against unsupported versions. If the bug still exists it should be re-reported against a current version with a fresh stack trace.
Recommended Actions
Note: Issues appear in multiple categories where criteria overlap. Snapshotted against open issues as of 2026-04-30.