Crash when rendering huge images on CPU 2.92.0 alpha #82042
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#82042
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?
2.92.0 alpha is crashing when rendering huge images around 20.000px in width and 10.000 in height.
2.91.0, Commit date: 2020-10-31 20:46, Hash
30826a5e49
- have this problem also.2.90.1 hash:
3e85bb34d0
don't have this problem.Additional information is that in 2.92 after lowering the resolution so the render can start, the CPU is utilized only in ~80%.
Steps to reproduce:
system-info.txt
crash.crash.txt
crash.blend
blender_2.91.0_crash.txt
Added subscriber: @silex
Crash when rendering huge images on CPUto Crash when rendering huge images on CPU 2.92.0 aplhaCrash when rendering huge images on CPU 2.92.0 aplhato Crash when rendering huge images on CPU 2.92.0 alphaAdded subscriber: @iss
Changed status from 'Needs Triage' to: 'Needs User Info'
I see following error message, so I can't check this with my GPU.
I see a lot of addons enabled, please click on File > Defaults > Load Factory Settings and re-check this to exclude influence of addons.
Thanks for checking this.
I should have mentioned that I dont use GPU for rendering - Cycles on CPU only.
After aplying factory defaults:
crash_2.blend
crash_2.crash.txt
The only thing that I changed were:
I couldn't reproduce crash, but I was unable to render such large image in 2.92. Rendering was very slow and got stuck on ~1%
Changed status from 'Needs User Info' to: 'Confirmed'
Thank you. I want co confirm, that on recent builds the problem persists - after launching Blender from command line I got segfault as before.
The crash occurs straight after launching render. There is no error message either.
On the surface it looks very similar to when rendering scene is too big for VRAM. But now this happens with CPU rendering.
Maybe this could be related to recently implemented tile stealing?
Added subscriber: @Jeroen-Bakker
Done quick profiling, lot of time is spent inside
scaledownx()
so will change tags.Crash happens when generating the GPU texture.
@Jeroen-Bakker There seems to be also significant performace regression with same conditions (rendering large image). I thought it could be reason of crash but it isn't.
I have made new report for this #82591
This issue was referenced by
2e1498ff16
Changed status from 'Confirmed' to: 'Resolved'