Q100081: Troubleshooting different types of Mari issues



This article describes the essential steps to follow for identifying and solving various issues in Mari.


Project Corruptions

If your project suddenly no longer opens and appears to be beyond retrieval then you may want to attempt to restore your project from a backup using the method described here: Q100039: Restoring a Mari project from a backup.

Viewport issues and glitches

As most issues with the Viewport are GPU related, you should always ensure you've updated your GPU driver to the latest version. If the issue persists, try launching Mari in safer mode as this test will temporarily reset your user preferences, and customisations, and disable plugins. If the problem still appears in safer mode check if the geometry has any shortcomings like overlapping faces, incorrect normals, or topology issues.

Startup Crashes

Startup problems can have several causes and the most common ones are explained here: Q100041: Mari launch issues
We also recommend testing launching Mari in safer mode, as this will help to establish whether the crash is being caused by a configuration/plugin issue, or by a core Mari component.

Performance issues

This is dependent on the Project and on your Mari setup. We recommend checking the following two articles, as one describes best practices and setups for optimal performance, while the other could indicate which hardware component on your machine may be getting overloaded:

Q100188: Improving performance in Mari and in specific Projects
Q100078: Mari's usage of hardware components

Furthermore, we recommend testing performance by launching Mari in safer mode to check if specific user settings or plugins are causing slowness.



If you are still experiencing difficulties please create a Support ticket and provide us with the information requested in this article:
Q100090: Reporting a Mari issue

For more information on how to open a Support request, please refer to this article:
Q100064: How to raise a support ticket

    We're sorry to hear that

    Please tell us why