Maniphest T97118

Error when closing the program
Closed, Archived

Assigned To
None
Authored By
Konstantin (Beaver95)
Apr 6 2022, 6:57 PM
Tags
  • BF Blender
Subscribers
Germano Cavalcante (mano-wii)
Konstantin (Beaver95)
Pratik Borhade (PratikPB2123)

Description

System Information
Operating system: Windows 10
Graphics card: NVIDIA GeForce RTX 1050 Ti

Blender Version
Broken: 3.1.2

Short description of error
When the program closes, a message appears on the command line

Blender quit
Error: Not freed memory blocks: 4, total unfreed memory 0.000458 MB

Exact steps for others to reproduce the error

Event Timeline

Konstantin (Beaver95) created this task.Apr 6 2022, 6:57 PM
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Apr 6 2022, 11:00 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).

Not much information for us to tell what's going on.

Please open Blender's installation directory and double click on the blender_debug_log.cmd.
This will start Blender in debug mode and create log files. Try to reproduce the error again.
Once you close Blender, the Windows Explorer should open and show you up to two files, a debug log and the system information.
Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop.

Pratik Borhade (PratikPB2123) added a subscriber: Pratik Borhade (PratikPB2123).Apr 7 2022, 5:33 AM

I found the likely culprit: The latest release of BlenderKit Online Asset Library v3.1.0. Disabling this add-on fixes the issue.

So please disable Blenderkit add-on and see if that fixes the memory leak

Konstantin (Beaver95) added a comment.EditedApr 7 2022, 9:37 AM

At the moment, I found that the addon "Adobe Substance 3d add-on for Blender" or addon "Blender Kit" (probably) is the source of the problem

Konstantin (Beaver95) added a comment.Apr 7 2022, 9:45 AM


@Germano Cavalcante (mano-wii) I reproduced the error and got logs like this

Germano Cavalcante (mano-wii) closed this task as Archived.Apr 7 2022, 3:43 PM

The problem is that some custom GPUShader has not been freed.
This was probably caused by some addon.

Unfortunately neither the Adobe Substance 3d add-on for Blender nor the Blender Kit are officially supported by blender.
I suggest reporting the issue to the author of the addon.