blender crash memory max #68528

Closed
opened 2019-08-11 04:39:59 +02:00 by HF · 12 comments

System Information
Operating system:win 10
Graphics card: 2070 super
32g ram
ryzen7 3700x

Blender Version
2.80.75

Short description of error
when i use texture mask to paint blender will freeze and ram usage will go up to max. it causes my pc to reboot once. after that during my testing, pc didnt reboot, just freeze

Exact steps for others to reproduce the error
i have the file for u. its all set up to the point i crash, i packed all file(with my brush all set up). all u need to do is to click the left mouse button on to the cube and blender will crash. i also have a video. i have this log file as well it says "Invalid in-ram queue size (20971520), adjusted to max ram queue size" might be useful.{F7658214}bug.blend

VID_20190810_213128_01.mp4

**System Information** Operating system:win 10 Graphics card: 2070 super 32g ram ryzen7 3700x **Blender Version** 2.80.75 **Short description of error** when i use texture mask to paint blender will freeze and ram usage will go up to max. it causes my pc to reboot once. after that during my testing, pc didnt reboot, just freeze **Exact steps for others to reproduce the error** i have the file for u. its all set up to the point i crash, i packed all file(with my brush all set up). all u need to do is to click the left mouse button on to the cube and blender will crash. i also have a video. i have this log file as well it says "Invalid in-ram queue size (20971520), adjusted to max ram queue size" might be useful.{[F7658214](https://archive.blender.org/developer/F7658214/aria-debug-10412.log)}[bug.blend](https://archive.blender.org/developer/F7658215/bug.blend) [VID_20190810_213128_01.mp4](https://archive.blender.org/developer/F7658226/VID_20190810_213128_01.mp4)
Author

Added subscriber: @Hongyu

Added subscriber: @Hongyu

Added subscriber: @rjg

Added subscriber: @rjg

I can confirm that drawing in texture paint mode does allocate quite a bit of memory. The texture that is painted on is present in the material as texture node, but disconnected. If this texture node gets deleted from the material it works fine. It does lag a bit, but that is due to the large image size of both the texture and the brush.

The log file you attached has nothing to do with Blender. It seems that this is from Aria which is part of the OneDrive app.

@ZedDB @ideasman42 This may be something for you.

I can confirm that drawing in texture paint mode does allocate quite a bit of memory. The texture that is painted on is present in the material as texture node, but disconnected. If this texture node gets deleted from the material it works fine. It does lag a bit, but that is due to the large image size of both the texture and the brush. The log file you attached has nothing to do with Blender. It seems that this is from Aria which is part of the OneDrive app. @ZedDB @ideasman42 This may be something for you.
Author

hi, thanks for the reply, so u are saying that u didn't crash when painting. so how much memory were u using with my file. with file that small. using all 32gb of my memory is obviously a bug. the log file i acquired from the blender path file, along with other log files and .blend autosave. can this be the reason why i am crashing and using all my memory? one drive somehow messed thing up?

hi, thanks for the reply, so u are saying that u didn't crash when painting. so how much memory were u using with my file. with file that small. using all 32gb of my memory is obviously a bug. the log file i acquired from the blender path file, along with other log files and .blend autosave. can this be the reason why i am crashing and using all my memory? one drive somehow messed thing up?

Added subscribers: @ZedDB, @ideasman42

Added subscribers: @ZedDB, @ideasman42

Blender definitely allocates a lot of memory in this case, I stopped it before swapping. The directory where Blender stores temporary files C:\Users\cyber\AppData\Local\Temp\ is used by other applications as well. The error message in that log file does indeed look like OneDrive/Aria it's trying to allocate too much memory as well, so it could make the situation worse.

Blender definitely allocates a lot of memory in this case, I stopped it before swapping. The directory where Blender stores temporary files `C:\Users\cyber\AppData\Local\Temp\` is used by other applications as well. The error message in that log file does indeed look like OneDrive/Aria it's trying to allocate too much memory as well, so it could make the situation worse.

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2019-08-12 10:39:23 +02:00

We cannot do much here, if you run out of RAM you run out of RAM, and Blender will almost certainly crash. Improving efficiency is always a goal, but that's not a bug. Thanks for the report anyway.

We cannot do much here, if you run out of RAM you run out of RAM, and Blender will almost certainly crash. Improving efficiency is always a goal, but that's not a bug. Thanks for the report anyway.

I'm not familiar with how memory is allocated in texture paint mode, but something seems to be going wrong. If I run the Blender file as is, it will run out of memory. However if I delete the unconnected node that reference the texture that is painted on, it will peak at about 4 GB.

Texture node in the shader that is disconnected but heavily impacts memory allocation.
node_shader.jpg

Aborted run that allocates until out of memory
with_node_in_shader.jpg

Project without the texture node
without_node_in_shader.jpg

I also noticed that the texture isn't displayed in the image editor, but when the texture node is removed it displays correctly. Furthermore the perspective in the texture paint mode changes when the texture node is removed, which is very strange.

Texture paint workspace when loading the file
loaded.jpg

Texture paint workspace after removing the texture node in the shading workspace
node_removed.jpg

This was tested with 52421e9ace

I'm not familiar with how memory is allocated in texture paint mode, but something seems to be going wrong. If I run the Blender file as is, it will run out of memory. However if I delete the unconnected node that reference the texture that is painted on, it will peak at about 4 GB. Texture node in the shader that is disconnected but heavily impacts memory allocation. ![node_shader.jpg](https://archive.blender.org/developer/F7660111/node_shader.jpg) Aborted run that allocates until out of memory ![with_node_in_shader.jpg](https://archive.blender.org/developer/F7660106/with_node_in_shader.jpg) Project without the texture node ![without_node_in_shader.jpg](https://archive.blender.org/developer/F7660108/without_node_in_shader.jpg) I also noticed that the texture isn't displayed in the image editor, but when the texture node is removed it displays correctly. Furthermore the perspective in the texture paint mode changes when the texture node is removed, which is very strange. Texture paint workspace when loading the file ![loaded.jpg](https://archive.blender.org/developer/F7660113/loaded.jpg) Texture paint workspace after removing the texture node in the shading workspace ![node_removed.jpg](https://archive.blender.org/developer/F7660115/node_removed.jpg) This was tested with 52421e9ace74

@mont29 Can you have another look at this?

@mont29 Can you have another look at this?

@rjg cannot confirm that here, for me deleting the unlinked texture node does not prevent Blender from eating all available RAM for me...

@rjg cannot confirm that here, for me deleting the unlinked texture node does not prevent Blender from eating all available RAM for me...
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser Project (Legacy)
Interest
Asset System
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#68528
No description provided.