Blender 2.8: Crash with background nodes #52385
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#52385
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 64 GTX 970
Blender Version
Broken: First bad commit: https://developer.blender.org/rB2eef097831caf14634cc0fc6749b857096baf3da#2816e222 (git bisect)
Short description of error
Crash when enabling eevee background nodes (windows 32 build)
Exact steps for others to reproduce the error
Changed status to: 'Open'
Added subscriber: @you.le
this patch: http://pasteall.org/509540/diff fixes the issue but I'm not sure this is correct
Added subscriber: @fclem
Note that D2788 solve this. But I would prefer this to be investigated / reviewed more to be sure this crash comes effectively from theses strings.
Added subscriber: @dfelinto
@you.le without a crash report (full backtrace from a debug build) we can't handle this for now.
backtrace: http://pasteall.org/pic/show.php?id=118468
blender.exe -d: http://pasteall.org/545272
file I used to produce the crash: http://pasteall.org/blend/index.php?id=47708 (just click on use nodes in world panel)
The bug occurs on my computer on windows 10 64 bits only with windows 32 builds. I'll update if I have more infos. in upbge I fixed it like in the patch except that I changed again this:
GPU_DATATYPE_STR[18] -> GPU_DATATYPE_STR[17]
and
for (i = 1; i <= 17; i++) {
if (GPU_DATATYPE_STR- [x] && gpu_str_prefix(code, GPU_DATATYPE_STR[i])) {
type = i;
break;
}
}
(17->16)
But I didn't investigated much on this. I noone can reproduce the bug, I'll try to investigate more
It happens only when I build myself (both Visual studio 2013/2015). I'll redownload libraries to see. Sorry about the time you spent on this
Added subscriber: @LazyDodo
It's not just you, i have no issues reproducing a crash with
@LazyDodo: Thanks very much for the test. I'm currently reinstalling all my dev environment. But if I'm not alone to have this bug...
@dfelinto && @fclem: If we don't find the cause of the bug, is there any inconvenience to put Closure at 5 instead of 17? (I saw that in GPU_material.h there is a comment which says that normally the number must correspond to the data components number: vec4 -> 4... but for Closure the number is not static?).
Moving closure is probably just going to mask the problem. I can't put my finger on it, but it does seem like a codegen bugs in the 32bit compiler
This works just as well, and gets rid of 'magic' constants in the code at the same time..
I reinstalled all my environment ("Repair"ed MSVC 2013, reinstalled git, tortoise git, tortoise svn, cmake, redownloaded libs, blender sources, cleared the cache in AppData/Roaming).
@LazyDodo: I copied the 2 lines of your patch but it doesn't work for me (tested @7dfcbe)(last sources)
This: http://pasteall.org/545633/diff prevents the crash for me but I have no idea if this is good or not.
The other bug I opened at the same time: https://developer.blender.org/T52392 is still there for me when I apply my patch. So maybe this is my patch which cause this bug.
I noticed 2 differences since the last time I tested blender2.8 branch:
In the version from builbot (same hash):
I don't know if the current bug and https://developer.blender.org/T52392 are related. I have no idea on how to fix it.
About crash for background:
I'll try to study that later.
I'm very often connected to irc and if a dev wants to help on this bug, I can give distant access/control over my computer via team viewer.
notes: It's weird that I have not exactly the same behaviour between my computer and build from buildbot (but the version from buildbot has similar issues too). I don't know if we can access the buildbot specs. Mine are Windows 10 64 bits, Visual Studio 2013 update 5, GTX 970, intel i7 2600k.
Feel free to ask for more infos.
Nah i'm still getting bad vibes from this, i'd rather get to the bottom on it than move closure to a different spot 'cause that doesn't crash' , pretty sure all it would do is mask the actual problem.
also please attach any crashlog, regular log or .blend file directly to the ticket rather than hosting them off site, (you can just drag files onto the text box and it'll upload automagically)
Anyhow there's one crash with worldNodesCrash.blend , how do i repro the second one ?
@LazyDodo: in this file: http://pasteall.org/blend/index.php?id=47719 (I didn't change anything, I saved it with last blender2.8 sources with my windows 32 debug build), just click on use nodes in the material panel. For me it crashes.
oops sorry, drag and drop:
materialNodesCrash.blend
Allright, found it, and can also explain why moving closure to 5 'fixes' it
in gpu_codegen.c in gpu_node_input_link we have the following catch all
and in the typedf for GPUInput we have this for vec
Given the type for closure is 17, this will copy 17 floats from link->ptr1 neatly overwriting input->link with garbage.
This gets later dereferenced and boom we go
@fclem / @dfelinto , I'll leave the fixing up to you guys.
Goddmanit ! Thank you so much @LazyDodo this is a major time savoir.
This issue was referenced by
3b080c3f66
Changed status from 'Open' to: 'Resolved'
Thanks!