Crash when playback preview rendering volume in cycles possibly due to overload #67076
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
6 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#67076
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: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 970/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 430.86
Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash:
06312c6d2d
Worked: (optional)
Short description of error
When I playback my smoke simulation in cycles preview rendered view it can't render the frames as fast as it needs to which leads to a crash.
Exact steps for others to reproduce the error
blender.exe: EXCEPTION_ACCESS_VIOLATION at 0x00007FF7D69FXXXX (last digits are different every time)
Added subscriber: @McLP
Added subscriber: @dark999
this bug is not reproducible on OpenSUSe Tumbleweed linux CPU AMD FX8350, 16G ram, GPU Nvidia GTX690
System-Info_blender-2.80-af51988115d4.txt
i played simulation for more than 10 minute and it is not crash or error
.blend file was setting for CPU Cycles rendering, i test this file with GPU Cycles rendering, same result
Tomorrow I'll try it myself on more PCs and systems. my cpu is a little older (FX6300 iirc) but I think it may have something to do with windows.
or maybe some kind of hardware problem like ram or power supply or a bad overclock configuration if you use it
Added subscriber: @ZedDB
Let us know how it goes. (I can't reproduce this on my end either)
I'd wonder if it was a hardware problem since I don't have any other issues. but I can't reproduce on my laptop either. but it is neither a ram nor a vram problem, they are doing just fine. can I get blender to output a more detailed crash report?
You will have to compile blender yourself to get a debug build.
What CPU do you have? Does your CPU pass some stresstests?
my cpu/gpu/ram are passing stresstests (did prime95,FurMark,etc). when i run the blender_debug_gpu.cmd, the last lines are always similar to this (crash occurs when mapping memory (but not the first time, only later), always same address now):
Just to be sure, does this happen with the latest blender beta? https://builder.blender.org/download/
still happens on RC2
but it does not crash in debug mode, only in normal use. That's wierd.
Oh, it does, but it takes a lot more efford to overload.
another log... I needed to rotate the view to the following position and zoom in a bit to get a crash.
sorry for postig so many messages, i think i found another clue now - shortly before the crash, the frame rate goes up to about 20-60fps while it is not showing any new frames and before the crash it would at maximum be around 5-15 fps. edit: not only shortly before but sometimes a bit longer. but it does not crash at low fps.
btw, I just tried it with blender 2.80 (not rc) on my laptop (Lenovo X230, not the pc I first encountered it). still crashes.
Added subscriber: @iss
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
I was able to reproduce this only in release build. I wasn't able to build smoke cache in debug
Added subscriber: @mont29
@iss would still be useful to have a minimal backtrace to identify in which part of the code it happens I guess?
Backtrace to crash:
Got this using RelWithDebInfo, in debug this file barely renders...
Added subscriber: @brecht
Changed status from 'Confirmed' to: 'Resolved'
This should be fixed by
e6d0a43
.