Help

Crash reports and problem reports

What Arx keeps when it crashes, and how Report a Problem opens a GitHub issue for the Arx team.

Arx sends nothing about how you use it. It has no usage statistics or analytics, and it never sends crash reports. To tell the Arx team about a problem, you open an issue on GitHub yourself.

Crash reports

When Arx or one of its helper processes (the parts that draw web pages, use the graphics card or load from the network) crashes, Arx keeps a short report on your Mac for 30 days, so you can add recent ones to a problem report. They stay on your Mac.

A crash report holds:

  • Which part of Arx crashed, such as Arx itself or the page renderer.
  • Where in Arx's code it crashed: the names of Arx's and macOS's code files and positions in them, and the function names macOS adds.
  • The kind of crash, such as a bad memory access.
  • The versions of Arx, its engine and macOS, and when the crash happened.

A crash report never holds:

  • Web addresses, page titles or anything from a page.
  • Anything from your Mac's memory, your files or their names and folders.
  • Your name, your account name, or any identifier for you or your Mac.

Settings → Privacy shows how many crash reports Arx keeps. Remove deletes them, the freezes and unexpected quits it noted, and the problem report files Arx saved. macOS and Arx's engine keep their own crash files too; Arx only reads them.

Freezes

When Arx stops responding for a second or more, it notes the freeze on your Mac: when it began, how long it lasted, and where in Arx's code it was stuck, in the same form as a crash report. macOS also gives Arx a daily summary of its freezes, which Arx keeps the same way. Both stay on your Mac for 30 days, hold nothing from your pages and never leave your Mac unless you attach them to a problem report.

Unexpected quits

Some quits leave no crash report: Force Quit, macOS ending Arx to free memory, or the Mac restarting. Arx notices them the next time it opens and notes each one: when it happened, the likely cause (a crash, a freeze, low memory, a restart, or unknown), Arx's version, and how many tabs and spaces you had. It never notes which tabs they were. These notes stay on your Mac for 30 days.

Report a Problem

Help → Report a Problem… (also in Settings → Privacy) opens a short form. Describe what went wrong and what you expected.

Open Issue on GitHub opens a new issue for the Arx team in a new tab, with these filled in:

  • What you wrote.
  • The versions of Arx, its engine (Helium and Chromium) and macOS, and your Mac's processor type.

With Include diagnostics on, which it is unless you turn it off, Arx first saves a report file with your Mac's model and memory and the crash reports, freezes and unexpected quits from the last 7 days, and selects it in Finder. Drag the file into the issue's Diagnostics box to attach it. The issue only names the file; nothing from it goes along unless you attach it.

Check the issue before you submit it, and change or remove anything you like. You need a GitHub account to submit it, and the Arx team answers you there.

After the issue opens, the form stays to show the report file's name and folder, with Show in Finder. While the Arx repository isn't public yet, GitHub may say the issue page can't be found. Then send the file to the Arx team another way, or use Save Report… when no file was saved.

Save Report… saves the same report as a file wherever you choose, to read it first or share it another way.