Crash within a few tries of attempting to render the scene with EEVEE and Freestyle enabled #56015
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#56015
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
Windows 10 Pro 64 bit (1803)
AMD Radeon RX480 4GB with Radeon Software 18.7.1
Blender Version
Broken: Latest Blender 2.8 build with Visual Studio 2017 (
7c8e6048b3
)Short description of error
Blender crashes when attempting to render the image with the Eevee rendering engine and Freestyle is enabled.
This does not necessarily happen right away, but within a few tries the program eventually crashes with the following generic error from the command line:
Exact steps for others to reproduce the error
Additional notes
Does not appear to crash when Cycles is the default renderer.
I realize that Freestyle in general does not support Eevee correctly yet.
Added subscriber: @s12a
Added subscriber: @mont29
Cannot reproduce the crash here with linux (debian64 testing)… :/
To make sure I wasn't having problem with my building environment, I tried to download the latest Windows 64bit build from Buildbot as of writing (git20180716
dc3b3d9453
).After repeating the above procedure (load factory settings, enable Freestyle, F12 render) I still managed to eventually reproduce the bug. However, in one instance it required several tries, and in another one Blender didn't appear to crash within a reasonable number of tries (but it did after restarting the program). In a last attempt it crashed right away.
Added subscriber: @ChristopherAnderssarian
Can't confirm on Windows 7
Rendered correctly with no crashes 15+ times.
with
dc3b3d9453
It could be a GPU vendor-specific issue. What GPU are you using? I just tried again with the latest buildbot build, and it crashed on the first attempt, by the way.
Furthermore, when it does not crash, all I'm getting a black screen render (but with Cycles, Freestyle works correctly). I previously assumed that this functionality is simply not working in general with EEVEE, but perhaps it's a related GPU-specific bug? I didn't report it due to the bug tracker currently being open only for crashes.
Quadro FX 1800
If you check the Z-Buffer you should see the cube.
Yeah, not implemented yet.
Upon further testing I managed to get it to crash.
After tweaking the line thickness and running --debug
I got this:
Could be a lot of things, but would suspect some OpenGL issue… Can you please run it with
--debug-gpu
option and attach as text file here any error printed out in the console (do not paste it directly in comment)? Thanks. Also maybe worth trying with-t 1
option (to run in single-thread mode).@fcelm, maybe you have better ideas about what to try here?
@mont29
This time I even used a debug build, quickly obtaining a crash within 1-2 attempts of rendering the image with Freestyle enabled, as of
e91bdb10e9
. Note that it says RX580 but it's actually an RX480 (there should be no difference OpenGL-wise; this is due to a GPU modification).Console output with
--debug-gpu --factory-startup
debug_info_1.txt
Console output with
--debug-gpu --factory-startup -t 1
debug_info_2.txt
Also attached:
blender.crash.txt
As of Blender 2.8
f08f6c1ade
I'm not able to reproduce the above issue anymore (with a release build). Freestyle still doesn't get rendered correctly with EEVEE (F12 render shows a black screen), but I guess that's to be expected at this stage.Changed status from 'Open' to: 'Resolved'
Eeeeh ok, then I guess we can close as solved. :)
As I went to confirm that this bug got resolved I found that F12 rendering now doesn't work at all (Blender doesn't crash, but it freezes and must be forcibly closed), either with release or debug builds, and regardless of whether Freestyle is enabled or not. This only happens when EEVEE is the active Render engine.
However this is a different bug.