Re-creating a window after an inturrupt can crash and leak memory
Open
- Dominant language
- C
- Stars
- 8
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
When interrupting code in Dyalog, it is very common to skip steps in execution or jump past cleanup code. This causes resource leaks and crashes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the window creation and destruction paths, especially what happens when Dyalog execution is interrupted and cleanup is skipped. Done means recreating a window after an interrupt no longer crashes or leaks resources; the issue does not name specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100