Page MenuHome

Crashes and freezes with hair and motion blur
Closed, ResolvedPublic

Description

System Information
Operating system: Windows 10
Graphics card: GTX 1070

Blender Version
Broken:
version: 2.80 (sub 35), branch: blender2.8, commit date: 2018-12-03 00:27, hash: a205493426b, type: Release

Short description of error
Rendering scene with hair + motion blur + progressive refine crashes.

Exact steps for others to reproduce the error

  1. Open attached file.
  2. Render -> Crash.

Also checked the following:
CPU Render + Motion Blur + Progressive Refine -> Crash
CPU Render + Motion Blur + No Progressive Refine -> OK
GPU Render + No Motion Blur + No Progressive Refine -> OK
GPU Render + Motion Blur + Progressive Refine / No Progressive Refine -> Starts Rendering, then freezes.

EDIT
All cases from above work if the Speed Vector Pass is not delivered (switch is on in the attached file!).


Event Timeline

Duplicated crash here (self-build current 2.8, Windows 10, Nvidia 1060) as described on the first try, but after a few more tries it seems to fail only around 60% of the time and otherwise starts rendering fine. The .blend looks like it was originally created in 2.79? Loading the .blend gives the following lines in the console (and they're repeated on hitting F12):

Read blend: C:\Users\Gavin\Desktop\Blender\hair_motion_blur_crash.blend
add_relation(NTree->Light Parameters) - Failed, but op_from (ComponentKey(NTShader Nodetree, SHADING)) was ok
add_relation(NTree->Light Parameters) - Could not find op_to (ComponentKey(LAPoint.000, PARAMETERS))
add_relation(Light -> Object) - Failed, but op_from (ComponentKey(LAPoint.000, PARAMETERS)) was ok
add_relation(Light -> Object) - Could not find op_to (ComponentKey(OBflamme_licht_links, PARAMETERS))
add_relation(NTree->Light Parameters) - Failed, but op_from (ComponentKey(NTShader Nodetree, SHADING)) was ok
add_relation(NTree->Light Parameters) - Could not find op_to (ComponentKey(LAPoint.005, PARAMETERS))
add_relation(Light -> Object) - Failed, but op_from (ComponentKey(LAPoint.005, PARAMETERS)) was ok
add_relation(Light -> Object) - Could not find op_to (ComponentKey(OBflamme_licht_mitte, PARAMETERS))
add_relation(NTree->Light Parameters) - Failed, but op_from (ComponentKey(NTShader Nodetree, SHADING)) was ok
add_relation(NTree->Light Parameters) - Could not find op_to (ComponentKey(LAPoint.006, PARAMETERS))
add_relation(Light -> Object) - Failed, but op_from (ComponentKey(LAPoint.006, PARAMETERS)) was ok
add_relation(Light -> Object) - Could not find op_to (ComponentKey(OBflamme_licht_rechts, PARAMETERS))

Crash message:

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF69CBB0A22
Error : EXCEPTION_ACCESS_VIOLATION
Module : G:\bdev\build_windows_Release_x64_vc15_Release\bin\Release\blender.exe

The console output is a relict of some driver stuff the file contained, may be another issue. I figured out that the crash is related to enabling Vector Pass output. If the switch is off all cases from above work. Going to update the description.

Sebastian Parborg (zeddb) lowered the priority of this task from 90 to 50.

I'm getting this assert in the debug build:

blender: /home/zed/programmering/blender_master/blender/intern/cycles/kernel/../kernel/closure/bsdf_hair_principled.h:223: int ccl::bsdf_principled_hair_setup(ccl::ShaderData*, ccl::PrincipledHairBSDF*): Assertion `fabsf(h) < 1.0f + 1e-4f' failed.
Philipp Oeser (lichtwerk) changed the task status from Confirmed to Needs Information from User.Feb 10 2020, 2:52 PM

Checked this again (quite an old report, sorry this has been lying around for so long!)

However, I am unable to reproduce now in master (no crashes, no freezes).
That being said, also checked in rB957b4547aeeb: Cleanup: Remove unused MTex.texflag (build from that time) and also did not experience those issues there.
So I would kindly ask if you could check again if this still an issue in a fresh build from https://builder.blender.org/download/?
Thx for checking... will put on hold for the time being...

Aaron Carlisle (Blendify) closed this task as Resolved.Feb 18 2020, 7:33 PM
Aaron Carlisle (Blendify) claimed this task.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.