In T95495#1304118, @Joshua Blömer (JYoshi) wrote:

I'm the developer of the realtime materials addon. I've managed to replicate the issue and am working on a fix now. For now the workaround is to run blender with the --factory-startup argument or to disable the addon in the preferences. The addon is not required to render the materials it's just a UI that makes appending the materials easier.

In T95495#1304038, @Germano Cavalcante (mano-wii) wrote:

Yes. As the "Realtime Materials" addon is not maintained by Blender, Blender does not provide support in this case.
The original author should be contacted and, if necessary, the author will contact the Blender's developers if it proves that the problem is in Blender.

In T95495#1304014, @Tom (Chf) wrote:

In case it helps find the root of the problem, I'm the developer of a standalone render manager and a couple of users reported a similar problem. Another add-on developer who faced the same investigated the issue and told me he found this error with a couple of addons:
"SystemError: GPU functions for drawing are not available in background mode"

In T95495#1303464, @Tom (Chf) wrote:

There's a few add-ons that seem to have started causing that in blender 3.0. Try using the argument --factory-startup so blender runs with default add-ons to see if that's the problem.

In T95495#1303402, @Germano Cavalcante (mano-wii) wrote:

I cannot reproduce this with either the latest stable or current development versions of Blender.
Whatever the version, the message "Blender quit" always appears at the end of the console.

Does this happen with any .blend file?
CPU rendering also causes this?
If you type the command in CMD instead of using a .bat file, does the problem also occur?