Relatórios de falhas

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.

O que você vê

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

Na janela:

1. O que você estava fazendo quando aconteceu? é opcional. Algumas palavras, como "Abri Adicionar URL", ajudam muito.
2. O relatório mostra tudo o que seria enviado. Leia-o primeiro, se quiser.
3. Enviar no GitHub abre o formulário Crash report do GitHub no seu navegador, já preenchido, junto com a pasta que contém o relatório. Arraste o arquivo do relatório para o formulário, verifique-o e envie. Você precisa de uma conta GitHub. Nada é enviado automaticamente.
4. Se alguém já relatou o mesmo problema, a janela informa (Já relatado como problema #…). Abrir o problema relatado o abre e coloca seu relatório na área de transferência, para que você possa adicioná-lo como um comentário.

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

O que um relatório contém

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

Ele não contém:

• seus endereços de download ou nomes de arquivo;
• seu nome de usuário, que aparece como ~ nos caminhos das pastas.

Se uma mensagem de erro citar algo que você digitou, esse texto estará no relatório, então leia-o antes de enviar.

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.

Onde os relatórios são mantidos

In GDM's data folder:

• crashes\: cada relatório (.txt) e seus dados de erro (.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 desenvolvedores

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.
• Lendo o dump. O monitor lê o dump com o rust-minidump da Mozilla. Ele usa os símbolos Breakpad da versão quando estão disponíveis. Uma compilação a partir do código-fonte também pode ler as informações de depuração nativas ao lado (seu .pdb, DWARF) quando compilada com --features mdm-crash/native-symbols; o aplicativo distribuído não inclui esse leitor, que ocupa vários MB. A Assinatura do relatório (por exemplo, freeze in misterdownloadmanager::winui::combo_edit) permanece a mesma nos relatórios de um mesmo problema, e a janela pesquisa problemas existentes por ela.
• Símbolos. As compilações de lançamento mantêm tabelas de linhas (debug = "line-tables-only"), mas nenhum download inclui as informações de depuração. O CI as transforma em MisterDownloadManager-<version>-symbols-<platform>.zip (tools/installer/symbols.py, usando o dump_syms da Mozilla), publicadas junto aos outros arquivos da versão. A janela de relatório busca o arquivo zip da própria versão quando uma pilha mostra endereços sem símbolos.
• Um .dmp de um 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.