Simple a GPencil object cause crashes Blender when use huge render resolution #94560
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#94560
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Linux-5.15.12-1-MANJARO-x86_64-with-glibc2.33 64 Bits
Graphics card: Mesa DRI Intel(R) HD Graphics 4600 (HSW GT2) Intel Open Source Technology Center 4.5 (Core Profile) Mesa 21.3.2
Blender Version
Broken: version: 3.1.0 Alpha, branch: makepkg (modified), commit date: 2021-12-31 20:32, hash:
6844304ddaWorked: (newest version of Blender that worked as expected)
Short description of error
I have a large scene with many objects. At some time, I got the issue - Failed to submit batchbuffer. No space left on device.
Bellow shown last log of full debug mode. The Blender completed render and got to another stage and is crashed:
I tried clean up the file and removed a lot objects in the scene but it don't help me. Also I have a similar scene and the same parameters and Blender doesn't crashing.
I'm sure this is some of issue with this file, not the device. 2 days ago it worked just fine and I didn't have the issue. Please see attached file.
Exact steps for others to reproduce the error
i965.blend
Added subscriber: @Wovchick
Added subscriber: @deadpin
We've had reports of several Arch-based Mesa driver problems recently. It seems a recent update there has caused a variety of problems; in particular for versions like 21.3.x.
It seems like you're already on the other task #94209. Can you check your update history and see when your Mesa driver was last updated? And/or can you try downgrading to 21.2 and see if that helps (it did for one other person).
But my problem showed up only two days ago and only when I use the attached file. I tested many different options with similar scenes and cannot reproduce the issue. I don't understand which cause it, I seem the Mesa is don't cause because the Mesa was upgraded more than two days ago and the problem didn't happen.
I tried to upgrade to Mesa 21.3.3 and to downgrade to 21.2.5 versions but nothing change for me, the issue remains
I watched log and seems got extended message from Mesa 21.2.5:
What is it?:
Freeing memory after the leak detector has run. This can happen when using static variables in C++ that are defined outside of functions.It may be cause? It is the message from Blender or Mesa?
I registered the Issue on Mesa Bug Tracker - https://gitlab.freedesktop.org/mesa/mesa/-/issues/5811
Below duplicate information from here: https://gitlab.freedesktop.org/mesa/mesa/-/issues/5811
I tried activate new driver from variable environment and so run the Blender.
The Blender crashes also but when I render full picture size. Previous the Blender example file which I attached earlier used render region and now Blender doesn't crash if used the
crocusdriver. But when I render full a picture then exactly the same happens, Blender is crash.I attached new version of example Blender file to Blender BugTracker where removed render region.
Also I collected and attach here coredump from systemd when the Blender is fall. May be it helps to resolve the problem?
Info and dump:
Coredump:
core.blender.1000.c9ed9951dcd84d9ca6d6a5e70804fc5f.5858.1641337189000000.zst
Open blend file and go to render layout and run F12.
i965.blend
After I changed driver i965 to Crocus, I no longer receive the error
i965: Failed to submit batchbuffer: No space left on device, Blender just crashes without any message.I continued looking for the reason crashes and found that in the example file which I attached early that the crash causes a Grease Pencil object -
Add -> Grease Pencil -> Strokeby default and when render setup to huge resolution, for example 10000x5000px.For reproduce the issue:
Add -> Grease Pencil -> StrokeThe Blender was run with option
--debug-alland I got its Log:Log.Crash.GP.Stroke.txt
New examples file for reproduce:
gp-object-stroke.blend
Also I cannot reproduce with any other objects this issue. Blender Rendering it succeeds any scene on 10000x5000px. I only have the issue with the GP object as it turned out.
Due to new circumstances, I renamed the issue to new title.
Crash. Failed to submit batchbuffer. No space left on deviceto Simple a GPencil object cause crashes Blender when use huge render resolutionAdded subscriber: @iss
@Wovchick can you specify how much RAM does your system have?
I have 32Gb RAM + 15Gb Swap
I attached new file log where you can see that Cycles Render realizing is fine on my PC:
But next something is happening that crashing Blender.
Full log (
--log "*" --log-level -1 --debug-all):gpencil-log.txt
gp-object-stroke.blend
A similar issue - https://developer.blender.org/T94706
Added subscriber: @lichtwerk
Changed status from 'Needs Triage' to: 'Needs User Info'
Could you please check again in a fresh build from https://builder.blender.org/download/daily/?, because there has been a related fix
8cd6d0fe68This comment was removed by @Wovchick
No, Blender crashes after render. I checked it with version: 3.2.0 Alpha, branch: master, commit date: 2022-01-31 23:10, hash:
95005bbe02Blender also crashes after full image rendering without messages with run parameters
$ ./blender --factory-startup --log "*" --log-level -1 --debug-all, I have only core dump.If I do cancel after half of render than I don't have crashes. The crash happens only at end of rendering of full image.
I pasted log after finish rendering event. Crash is after render on fresh build Blender:
Changed status from 'Needs User Info' to: 'Needs Triage'
Added subscriber: @mano-wii
I can't replicate the crash (I saw, however, another issue with the rendering tiles... investigating...).
System Information
Operating system:
macOS-12.2-arm64-arm-64bit 64 BitsGraphics card:
Apple M1 Apple 4.1 Metal - 76.3Added subscriber: @OmarEmaraDev
I noticed the compositor runs after rendering, does disabling the compositor setup have any effect on the crash?
No. I disabled post processing (Compositing and Sequencer) and have the crash
Added subscriber: @PratikPB2123
Changed status from 'Needs Triage' to: 'Needs User Info'
@Wovchick hi, can you still replicate the crash in 3.2 release? https://www.blender.org/download/
Hello! I tried to render example file (posted above) with Blender 3.3 alpha version and have the same the crash
Changed status from 'Needs User Info' to: 'Needs Triage'
Changed status from 'Needs Triage' to: 'Needs User Info'
The initial error in the report is no longer reproducible and the description no longer fits the actual issue. We probably need to update this report after all of this investigation or open a new report. Can you do that?
Changed status from 'Needs User Info' to: 'Archived'
No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.
Thanks again for the report. If the problem persists please open a new report with the required information.