Cycles fails to render when material contains UV mapped texture as volume input #46352

New Issue

gandalf3 · 2015-10-03T09:03:24+02:00

gandalf3 commented

2015-10-03 09:03:24 +02:00

System Information
Archlinux

Blender Version
Broken: 2.76 RC3

Short description of error
Cycles fails to get past sample 1 when a material uses a UV texture on a volume input (sometimes blender crashes or freezes, but this only happened twice).

I would expect it to ignore the nonsensical material and render otherwise normally.

Exact steps for others to reproduce the error

Open cycles_volume_UV_crash.blend
Enable viewport render

**System Information** Archlinux **Blender Version** Broken: 2.76 RC3 **Short description of error** Cycles fails to get past sample 1 when a material uses a UV texture on a volume input (sometimes blender crashes or freezes, but this only happened twice). I would expect it to ignore the nonsensical material and render otherwise normally. **Exact steps for others to reproduce the error** 1. Open [cycles_volume_UV_crash.blend](https://archive.blender.org/developer/F241857/cycles_volume_UV_crash.blend) 2. Enable viewport render

gandalf3 commented

2015-10-03 09:03:25 +02:00

Changed status to: 'Open'

gandalf3 commented

2015-10-03 09:03:25 +02:00

Added subscriber: @gandalf3

Wolfgang Faehnle commented

2015-10-03 21:08:35 +02:00

Added subscriber: @mib2berlin

Wolfgang Faehnle commented

2015-10-03 21:08:35 +02:00

Hi, cant reproduce crash or freeze but texture is not included.
Tested with own .png

Opensuse 13.2/64
CPU Intel #4200
4 GB Ram
GPU Intel GN 965

Cheers, mib

Hi, cant reproduce crash or freeze but texture is not included. Tested with own .png Opensuse 13.2/64 CPU Intel #4200 4 GB Ram GPU Intel GN 965 Cheers, mib

gandalf3 commented

2015-10-03 22:52:28 +02:00

Here's a .blend with the texture packed cycles_volume_UV_crash.blend

Here's a .blend with the texture packed [cycles_volume_UV_crash.blend](https://archive.blender.org/developer/F241979/cycles_volume_UV_crash.blend)

Wolfgang Faehnle commented

2015-10-04 12:48:11 +02:00

Hi, tested your new file with my workstation but no freeze or crash.
Preview render work until the 10 appointed samples .

Opensuse 13.2/64
Intel i5 3770K
GTX 760 4 GB
Driver 355.11

Hi, tested your new file with my workstation but no freeze or crash. Preview render work until the 10 appointed samples . Opensuse 13.2/64 Intel i5 3770K GTX 760 4 GB Driver 355.11

gandalf3 commented

2015-10-05 00:31:49 +02:00

Odd, fails every time for me.
Rendering on GPU freezes the display and renders the system unusable (need to reset)

Archlinux x86_64
Intel Xeon CPU E5420
GeForce GTX 460 766 MiB
4.5.0 NVIDIA 355.11

Odd, fails every time for me. Rendering on GPU freezes the display and renders the system unusable (need to reset) Archlinux x86_64 Intel Xeon CPU E5420 GeForce GTX 460 766 MiB 4.5.0 NVIDIA 355.11

Aaron Carlisle commented

2015-10-05 01:36:25 +02:00

Added subscriber: @Blendify

Aaron Carlisle commented

2015-10-05 01:36:25 +02:00

Nothing bad happening here no crash successful render

Brecht Van Lommel commented

2015-10-05 02:11:02 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2015-10-05 02:11:02 +02:00

It's easy to make this crash in a debug build, an assert will be triggered.

The issue is that shader nodes requests certain attributes depending if there is a surface shader with if(shader->has_surface). But they do not change the SVM code generation to disable looking up the attribute.

That should either be fixed, or the SVM attribute lookup code should be changed to not crash when looking up an attribute that was not requested. That was done as an optimization but in hindsight is probably too fragile.

It's easy to make this crash in a debug build, an assert will be triggered. The issue is that shader nodes requests certain attributes depending if there is a surface shader with `if(shader->has_surface)`. But they do not change the SVM code generation to disable looking up the attribute. That should either be fixed, or the SVM attribute lookup code should be changed to not crash when looking up an attribute that was not requested. That was done as an optimization but in hindsight is probably too fragile.

blender-admin commented

2015-10-05 11:45:03 +02:00

This issue was referenced by 91f1886b8e

This issue was referenced by 91f1886b8e010bdac32e8dbe6c244b7ff8b46abb

Sergey Sharybin commented

2015-10-05 11:47:16 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2015-10-05 11:47:16 +02:00

This is a bit of a tradeof between runtime check and memory usage by attributes which doesn't make sense. Since such a check was already done for geometry find_attribute() will add similar thing to SVM node.

We can check if we want to have attributes always copied to the device instead later.

This is a bit of a tradeof between runtime check and memory usage by attributes which doesn't make sense. Since such a check was already done for geometry `find_attribute()` will add similar thing to SVM node. We can check if we want to have attributes always copied to the device instead later.

Sergey Sharybin commented

2015-10-05 11:47:54 +02:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2015-10-05 11:47:54 +02:00

blender-admin commented

2015-10-11 14:54:29 +02:00

This issue was referenced by blender/cycles@77c4eddd8a

This issue was referenced by blender/cycles@77c4eddd8ac19f1ef78071a007b63e2c222eab24

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycles fails to render when material contains UV mapped texture as volume input #46352