haven't looked into this, but it's something we'll want to fix at some point.
Contributor guide
Tech stack
rust
Domain
desktopfrontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Rust programmingdruid framework basicsmacOS development environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
The issue lacks details. A contributor should first investigate the WinHandler::destroy lifecycle in the druid source code, particularly the macOS platform implementation in the `platform/mac` directory. They may need to reproduce the bug on macOS and add logging to understand when `destroy` is expected to be called versus when it actually isn't. Existing comments or related issues in the repository (e.g., #297) might provide clues. No linked PRs or assignees exist, so this is open for exploration.
