Cycles crash on specific frame render with motion blur enabled #77040

Closed
opened 2020-05-25 03:46:53 +02:00 by Brent Thurston · 15 comments

System Information
Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon R9 M395X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26

Blender Version
Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: 375c7dc4ca

Short description of error
Cycles render crashes on frame 35 of attached file with motion blur enabled. Turning off motion blur resolves the issue. Additionally, frames before 35 render blank or incorrectly but do not cause a crash. This crash does not happen when rendering with Eevee. This bug was encountered on the Mac and Linux versions of 2.82a, but not the Windows 10 version.

Exact steps for others to reproduce the error
Simply render frame 35 using Cycles with motion blur enabled. Half of a blank frame will render and then Blender will crash.

Thanks very much for your work : )

cycles render crash.blend

**System Information** Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon R9 M395X OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26 **Blender Version** Broken: version: 2.82 (sub 7), branch: master, commit date: 2020-03-12 05:06, hash: `375c7dc4ca` **Short description of error** Cycles render crashes on frame 35 of attached file with motion blur enabled. Turning off motion blur resolves the issue. Additionally, frames before 35 render blank or incorrectly but do not cause a crash. This crash does not happen when rendering with Eevee. This bug was encountered on the Mac and Linux versions of 2.82a, but not the Windows 10 version. **Exact steps for others to reproduce the error** Simply render frame 35 using Cycles with motion blur enabled. Half of a blank frame will render and then Blender will crash. Thanks very much for your work : ) [cycles render crash.blend](https://archive.blender.org/developer/F8551602/cycles_render_crash.blend)
Author

Added subscriber: @pictureboy

Added subscriber: @pictureboy
Member

Added subscriber: @Alaska

Added subscriber: @Alaska
Member

I personally had this issue on another project. It occurs when motion blur is enabled and a object is changing it's scale from 0 to a non-zero value on the frame you're rendering.

This issue persists in Blender 2.83 and 2.90 with builds from 22 of May.

I remember seeing a task a short while ago discussing this issue, but I'm having trouble finding it again. I will leave the decision of what to do with this task up to the developers.

Edit: I believe #75441 was the task I was looking for. It doesn't describe a crash, but it produces rendering artifacts.

I personally had this issue on another project. It occurs when motion blur is enabled and a object is changing it's scale from 0 to a non-zero value on the frame you're rendering. This issue persists in Blender 2.83 and 2.90 with builds from 22 of May. I remember seeing a task a short while ago discussing this issue, but I'm having trouble finding it again. I will leave the decision of what to do with this task up to the developers. Edit: I believe #75441 was the task I was looking for. It doesn't describe a crash, but it produces rendering artifacts.
Author

Good to know. Thanks for the info, Alaska : )

Good to know. Thanks for the info, Alaska : )
Member

@pictureboy I realized I never gave an explanation for how I worked around the issue.

In the project I worked on, I actually keyframed the render visibility of the objects so they would only be accounted for in rendering if they were a non-zero scale. This avoided the crashing entirely.

@pictureboy I realized I never gave an explanation for how I worked around the issue. In the project I worked on, I actually keyframed the render visibility of the objects so they would only be accounted for in rendering if they were a non-zero scale. This avoided the crashing entirely.
Author

That's a workable solution, kudos. I'm liking the Blender community. : )

That's a workable solution, kudos. I'm liking the Blender community. : )

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'

I could not reproduce the problem here?
Do you render with GPU or CPU?
Can you try with the latest daily build? https://builder.blender.org/download/


Operating system: Windows-10-10.0.18941 64 Bits
Graphics card: Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.50.01.05 26.20.15001.5006

I could not reproduce the problem here? Do you render with GPU or CPU? Can you try with the latest daily build? https://builder.blender.org/download/ ---- **Operating system:** Windows-10-10.0.18941 64 Bits **Graphics card:** Radeon (TM) RX 480 Graphics ATI Technologies Inc. 4.5.13586 Core Profile Context 19.50.01.05 26.20.15001.5006
Author

I was rendering with CPU on a Mac. The crash also occurred on the 2.83 beta. As mentioned earlier, the same file rendered on a Windows machine did not exhibit the crash.

Hope this helps.

I was rendering with CPU on a Mac. The crash also occurred on the 2.83 beta. As mentioned earlier, the same file rendered on a Windows machine did not exhibit the crash. Hope this helps.

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'
Member

Adding Linux as @pictureboy reported that this issue also occurs on Linux.

I am also able to reproduce the issue on Linux but booting into Windows and testing I am unable to reproduce the issue (as discussed by @mano-wii and @pictureboy)

Rendered using a Ryzen 9 3900X.

Adding Linux as @pictureboy reported that this issue also occurs on Linux. I am also able to reproduce the issue on Linux but booting into Windows and testing I am unable to reproduce the issue (as discussed by @mano-wii and @pictureboy) Rendered using a Ryzen 9 3900X.

Added subscriber: @brecht

Added subscriber: @brecht

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'

Changed status from 'Needs Developer To Reproduce' to: 'Resolved'
Brecht Van Lommel self-assigned this 2020-07-08 13:59:30 +02:00

This was fixed by e936633.

This was fixed by e936633.
Sign in to join this conversation.
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
4 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#77040
No description provided.