Q100729: Managing and sending Mari Crash Reports to Foundry

Pete

Updated: February 03, 2026 00:20

Created: January 20, 2026 15:57

SUMMARY

Mari 7.5v1 introduces a Crash Report Manager, which allows you to send Foundry reports of any crashes you experience. This information is invaluable to Mari’s development team, as it allows us to identify issues our user base run into regularly, and hopefully address them.

As such, this article explains how to use Mari's Crash Report Manager, and best practices for submitting crash reports.

MORE INFORMATION

How to create a crash report

If Mari crashes, the following dialog window should appear:

This window can also be opened in Mari without crashing it by selecting Help > Manage Crash Reports, allowing access to previous crash reports.

Please fill out all fields with as much information as you can provide, following the guidance in the next section of this article. Then you can send the report to Foundry by pressing Send Report.

NOTE: Once you send the report and close the Crash Report Manager, the report will be removed from Mari. If you’d like to keep the report and its files for future reference, you can save it before sending it.

After sending the report you’ll also get a Crash Report ID, which looks like this:

You can send us this ID through a Support ticket, as described in the section below, if you’d ever like to discuss the crash with us. The ID will allow us to find your report in our internal database for further investigation.

NOTE: Crash Reports should be sent before any further crashes occur, as the folder for DMP files has an 8MB size limit, which if reached will automatically start deleting older reports.

What to add to each field of the crash report

Name and Email - These allow us to identify Crash Reports that came from you, in case you reach out to the Support team to discuss them.

Feedback - Tell us the situation, conditions, and steps that led to the crash. The more information you provide here, the more likely it is that we’ll be able to take action based on the report.

Attachments - Add any files you think would help us reproduce the issue, such as screenshots. A MariLog.txt file can be particularly valuable.

Although the following article focuses on Support tickets, you can use it as further guidance on how to best describe your issue in a Crash Report:
Q100090: Information to send Support when reporting a Mari issue

How we use crash reports for data analysis

Crash reports uploaded with the Send Report option do not go to Foundry’s Support team. As such, you will not receive any responses or be contacted after submitting a Crash Report.

Reports are instead sent directly to a database monitored by our developers, to help find common patterns in crashes, and hopefully improve Mari’s general stability. However, keep in mind that the automatically generated report often doesn’t offer enough information for the development team to fix the specific bug that causes your crash.

How you can use crash reports in Support investigations

If you are experiencing a specific crash regularly that you’d like assistance with, then we recommend you contact Support for further investigation. Through collaboration, we can hopefully identify the bug and log it in our system, so that the team can consider implementing a fix in a future Mari release.

For this, you will need to raise a Support ticket and provide us with the Crash Report reference ID number (such as 384f827f-83da-4b22-b17f-881a38fffc66 from the example image above) along with the rest of the information outlined in the following article:
Q100090: Information to send Support when reporting a Mari issue

How to disable the dialog but still generate crash reports

In some scenarios, there may be little value to displaying the Crash Report Manager when Mari crashes. For example, artist machines in some studios aren’t connected to the internet, so reports can’t be sent to Foundry directly.

To completely disable the display of the Issue Reporter when a crash occurs in Mari, you can set the following environment variable:

MARI_NO_CRASH_PROMPT=1

Crash Reports will still be saved however, and can be accessed in Mari under Help > Manage Crash Reports. From here you can save out the report, by pressing Save Report…, and send it to Support if you require assistance.

To learn more about setting environment variables, see:
Q100015: How to set environment variables