Informes de errores

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.

Qué se ve

• 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.

En la ventana:

1. ¿Qué estaba haciendo cuando ocurrió? es opcional. Unas pocas palabras, como «Abrí Añadir URL», son de gran ayuda.
2. El informe muestra todo lo que se enviaría. Léalo primero si lo desea.
3. Enviar en GitHub abre el formulario de Informe de errores de GitHub en su navegador, ya rellenado, junto con la carpeta que contiene el informe. Arrastre el archivo del informe al formulario, revíselo y envíelo. Necesita una cuenta de GitHub. No se envía nada automáticamente.
4. Si alguien ya ha informado del mismo problema, la ventana lo indica (Ya informado como problema #…). Abrir el problema notificado lo abre y pone su informe en el portapapeles, para que pueda añadirlo como comentario.

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

Qué contiene un informe

• 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.

No contiene ninguno de estos datos:

• sus direcciones de descarga o nombres de archivo;
• su nombre de usuario, que se muestra como ~ en las rutas de las carpetas.

Si un mensaje de error cita algo que usted escribió, ese texto está en el informe, así que léalo antes de enviarlo.

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.

Dónde se guardan los informes

In GDM's data folder:

• crashes\: cada informe (.txt) y sus datos de bloqueo (.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.

Para desarrolladores

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.
• Lectura del volcado. El monitor lee el volcado con rust-minidump de Mozilla. Utiliza los símbolos Breakpad de la versión cuando los encuentra. Una compilación desde el código fuente también puede leer la información de depuración nativa junto a ella (su .pdb, DWARF) cuando se compila con --features mdm-crash/native-symbols; la aplicación distribuida no incluye ese lector, que ocupa varios MB. La Firma del informe (por ejemplo, freeze in misterdownloadmanager::winui::combo_edit) permanece igual en los informes de un mismo problema, y la ventana busca problemas existentes con ella.
• Símbolos. Las compilaciones de lanzamiento conservan las tablas de líneas (debug = "line-tables-only"), pero ninguna descarga incluye la información de depuración. CI la convierte en MisterDownloadManager-<version>-symbols-<platform>.zip (tools/installer/symbols.py, usando dump_syms de Mozilla), publicada junto a los otros archivos de la versión. La ventana de informes obtiene el zip de su propia versión cuando una pila muestra direcciones sin procesar.
• Un .dmp de un problema:

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.