Rapporti di arresto anomalo

If GolinksPRO Download Manager closes unexpectedly or stops responding, a crash report window opens. It shows what happened, lets you read the whole report, and can send it to the developers on GitHub. Each report helps fix the problem for everyone.

Cosa vedi

• GolinksPRO Download Manager closed unexpectedly: GDM crashed, or hit an internal error and closed.
• GolinksPRO Download Manager stopped responding: its window didn't answer for 8 seconds. GDM is still running, frozen. End and restart GDM closes the frozen copy and starts a new one. If GDM answers again by itself, the window says so.

Nella finestra:

1. Cosa stavi facendo quando è successo? è facoltativo. Poche parole, come "Ho aperto Aggiungi URL", sono di grande aiuto.
2. Il rapporto mostra tutto ciò che verrebbe inviato. Leggilo prima, se vuoi.
3. Invia su GitHub apre nel browser il modulo Segnalazione di arresto anomalo di GitHub, già compilato, insieme alla cartella che contiene il rapporto. Trascina il file del rapporto nel modulo, verificalo e invia il modulo. Serve un account GitHub. Non viene inviato nulla automaticamente.
4. Se qualcuno ha già segnalato lo stesso problema, la finestra lo indica (Già segnalato come issue #…). Apri la issue esistente la apre e copia il tuo rapporto negli appunti, così puoi aggiungerlo come commento.

The other buttons copy the report, open its folder, or start GDM again.

Cosa contiene un rapporto

• What happened: the error and the place in GDM's code where it happened.
• The stack: the place in GDM's code where it crashed or froze, and what every other part of it was doing.
• GDM's recent log: for example "command AddUrl" or "window opened: add-url".
• The system: GDM's version and how you installed it, your operating system and its version, the processor, the language and theme, and how many downloads and queues you have. These are counts only.

Non contiene nessuna di queste informazioni:

• i tuoi indirizzi di download o nomi di file;
• il tuo nome utente, che appare come ~ nei percorsi delle cartelle.

Se un messaggio di errore cita qualcosa che hai digitato, quel testo è incluso nel rapporto, quindi leggilo prima di inviarlo.

The crash data file (.dmp) is a snapshot of what GDM was running at that moment. It helps the developers most, but it can hold pieces of what GDM had in memory, such as download addresses, cookies and saved passwords. It is only attached when you tick Also attach the crash data.

Dove vengono conservati i rapporti

In GDM's data folder:

• crashes\: ogni rapporto (.txt) e i relativi dati dell'arresto anomalo (.dmp);
• logs\: GDM's log (mdm.log, with older ones as mdm.1.log and so on, 2 MB each).

GDM's data folder is %APPDATA%\misterdownloadmanager on Windows, ~/Library/Application Support/misterdownloadmanager on macOS, and ~/.local/share/misterdownloadmanager on Linux. In portable mode it is the data folder next to the program.

The log records what GDM does, so a report can show what led to a problem. To log more detail, start GDM with the environment variable MDM_LOG=debug.

Per gli sviluppatori

How it works: a second copy of GDM, the monitor, starts beside it with --crash-monitor. The crash code lives in crates/crash and crates/app/src/crash.rs.

• Catching problems. When GDM crashes (a Windows exception, a signal on Linux, a Mach exception on macOS), panics, or freezes, it asks the monitor for a dump. A freeze is a frame of the window running more than 8 s, seen by a watchdog thread that ignores time spent asleep. It times both parts of a frame: what GDM handles (the commands that come in, the clock of downloads, queues and the Scheduler), which runs minimized too, and the drawing; never the wait between frames. The watchdog also measures how much processor time the window thread got meanwhile, and the report says what that means: it ran all along (a loop), it waited in a lock or on I/O (a deadlock), or it hardly ran in ordinary code, which is a computer too busy to run GDM or slow to load it from disk, most likely not GDM's bug (those share one signature, freeze while the computer was busy). When the window thread is already back in the event loop by the time the dump is written, the freeze was over before the snapshot, so its stack can't explain it; those reports say so and share the signature freeze over before the snapshot. macOS doesn't measure it yet. The monitor then writes a minidump of every thread from outside, through minidumper and crash-handler. A crashed process never writes its own dump, which is how Firefox, Crashpad and Sentry do it too.
• Lettura del dump. Il monitor legge il dump con rust-minidump di Mozilla. Usa i simboli Breakpad della release, se li trova. Una build dai sorgenti può anche leggere le informazioni di debug native che ha accanto (il suo .pdb, DWARF), se è compilata con --features mdm-crash/native-symbols; l'app distribuita non include questo lettore, che occupa diversi MB. La Firma del rapporto (ad esempio freeze in misterdownloadmanager::winui::combo_edit) resta uguale nei rapporti relativi allo stesso problema e la finestra cerca issue esistenti con quella firma.
• Simboli. Le build di release mantengono le tabelle delle righe (debug = "line-tables-only"), ma nessun download include le informazioni di debug. La CI le converte in MisterDownloadManager-<version>-symbols-<platform>.zip (tools/installer/symbols.py, usando dump_syms di Mozilla), pubblicati accanto agli altri file della release. La finestra del rapporto scarica lo zip della propria versione quando uno stack mostra indirizzi senza simboli.
• Un .dmp da una issue:

cargo run -p mdm-crash --bin mdm-symbolicate -- crash.dmp MisterDownloadManager-<version>-symbols-windows-x64.zip

• Testing it. cargo test -p mdm-crash runs a real freeze, panic and crash (examples/crashy.rs) and checks each report's signature. To try it in the app, start GDM with MDM_CRASH_TEST=1, then run misterdownloadmanager /show crash-test:freeze (a deadlock; or spin, 12 s of a busy window thread, panic, crash, abort). cargo test -p mdm-app --test freeze_report -- --ignored does that in a copy of the app off the screens, its window visible and minimized.