Crash reports

When a part of HIPS Provider stops unexpectedly, it sends HIPS a crash report: where in its code it stopped, its versions, your GPU and driver, and its recent events. Never your files, what you do on this computer, or the work it ran. Every part reports: the daemon with its terminal view, the tray and menu-bar app, the Linux session helper, the updater, the crash watcher and the engines the daemon runs.

Crash reports are on until you turn them off, with the one setting crash_reports: in the terminal view, in the Settings window's Support part on Windows and macOS, on the command line or in the configuration file. Off, nothing more is sent, the queue on the computer is deleted at once, and HIPS refuses reports from that device; crashes still go to the local log.

00000000000000000000000000000000000000001hips-provider config set crash_reports false

• The report's own id, made on the computer, which part stopped and how: a panic, a native crash, an abort, an engine's exit, a hang, a failed update.
• When it happened, how long the part had run, and how many identical crashes the computer folded into this report.
• The app's version and build and its target; for an engine its name, version, backend and build, and the catalog model's id, or for a customer's model only that it was one.
• The operating system's version and build, and on Linux the distribution and kernel; the GPU's vendor, model and driver version.
• The failure: the signal or exception code, for an access fault whether it read or wrote and a class of the address, never its value; the exit code; a panic's location in HIPS's own code.
• The stack: each frame as a module and an offset, found on the computer, and each module by its file name only.
• The attempt ids in flight, the last content-free events of that part's own log, and the last numeric readings the app already sends.

• Memory of any kind, register values, a dump or a core file.
• Request content, prompts, outputs, weights, or an engine's own output.
• A customer model's reference, environment variables or command lines.
• Full paths, the computer's name, or any user or account name: a home folder's name is replaced before the report is queued, and HIPS refuses a report in which one survives.
• What you do on the computer.

The reports queued and sent are listed by time, part, kind and version, and each opens in full as the JSON that is or was sent: in the terminal view, in the Settings window's Support part, or with the commands below.

00000000000000000000000000000000000000001hips-provider crash list2hips-provider crash show <id>