9 comments (9 comments)0 reactions (0 reactions)0 assignees (0 assignees)Dart11,653 stars (11,653 stars)421 forks (421 forks)batch import
Platform: Windowsbughelp wanted
Description
This issue does not include a description.
Contributor guide
- Tech stack
- flutter
- Domain
- mobile
- 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.
- active
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- Flutter basicsDebugging crash on exit
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 40
- Research direction
- Investigate the crash on program close. Start by examining the app's lifecycle callbacks in the main.dart file and any custom window close handlers. Look for unhandled exceptions or errors in platform specific code (e.g., Windows or Linux). The issue mentions clicking the close button, so check for any event listeners on the window close action. Since it's a Flutter app, may need to inspect the engine layer or native runners.