The maxr debug builds come with an integrated error report utility. The error report is a collection of files intended to help the developer diagnose the cause of the crash: a crash minidump file, a crash description XML file, and other optional files.
What information will be sent?
In case of an application crash, the following information are sent to the maxr developer team:
- A binary memory dump of the maxr process. A crash minidump file (crashdump.dmp) contains operating system version, processor type, CPU registers state, local variables and call stack for each execution thread. The minidump file can be used on developer's side to determine the reason of the crash and try to fix the problem.
- A screenshot of the maxr window a the moment of the crash
- The maxr/resinstaller logfiles
- The configuration file, containing the current maxr settings (max.xml)
- optional: email address and problem description explicitly provided by the user
You can review the content of each sent file, before sending the report.
Who has access to the sent information?
The report is directly sent via an encrypted connection to the server of the maxr development team. Only members of the maxr dev team will have access to the reports. We do not share the reports with any other organization.
What is the information used for, and how long is it saved?
All information in the reports will only be used to solve the reported problem. The reports will be deleted as soon as the problem is fixed.