OSL: Cycles Script Node with trace call crashes Blender on render #54887

New Issue

Tim · 2018-04-29T19:17:37+02:00

Tim commented

2018-04-29 19:17:37 +02:00

System Information
Windows 10 64 bit, GTX 980 Ti, rendering on i9-7900X

Blender Version
Broken:
2.75a c27589e
2.78c e92f235283
2.79b f4dc9f9d68
2.79 5740505 (latest build)
2.79 60f4cb2 (latest build, win32)
2.80 cfa1700 (latest build)

Worked:
2.70 19e627c

Short description of error
A trivial OSL Script Node in Cycles where trace(a, b) and then getmessage("trace", hitdist", dist) is called and result is passed to mix node crashes Blender with EXCEPTION_ACCESS_VIOLATION on render. I experienced similar crashes even when trace/getmessage weren't being called, but this particular example was easiest to reproduce consistently.

Exact steps for others to reproduce the error
osl-bug.blend
Open attached .blend file, switch to rendered viewport shading or hit render to instantly crash Blender.

**System Information** Windows 10 64 bit, GTX 980 Ti, rendering on i9-7900X **Blender Version** Broken: 2.75a c27589e 2.78c e92f235283 2.79b f4dc9f9d68b 2.79 5740505 (latest build) 2.79 60f4cb2 (latest build, win32) 2.80 cfa1700 (latest build) Worked: 2.70 19e627c **Short description of error** A trivial OSL Script Node in Cycles where `trace(a, b)` and then `getmessage("trace", hitdist", dist)` is called and result is passed to mix node crashes Blender with `EXCEPTION_ACCESS_VIOLATION` on render. I experienced similar crashes even when trace/getmessage weren't being called, but this particular example was easiest to reproduce consistently. **Exact steps for others to reproduce the error** [osl-bug.blend](https://archive.blender.org/developer/F3123248/osl-bug.blend) Open attached .blend file, switch to rendered viewport shading or hit render to instantly crash Blender.

Tim commented

2018-04-29 19:17:37 +02:00

Added subscriber: @ptim

Philipp Oeser commented

2018-04-30 11:20:58 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2018-04-30 11:20:58 +02:00

Cannot reproduce here (checked official releases 2.79, 2.79a, 2.79b, 2.78c), but I'm on linux...
Someone on Windows being able to reproduce?

Cannot reproduce here (checked official releases 2.79, 2.79a, 2.79b, 2.78c), but I'm on linux... Someone on Windows being able to reproduce?

ChristopherAnderssarian commented

2018-04-30 11:32:01 +02:00

Added subscriber: @ChristopherAnderssarian

ChristopherAnderssarian commented

2018-04-30 11:32:01 +02:00

Cannot reproduce on 5960x CPU with 2.79a/b on Windows 7.

Through author probably used their GTX 980 Ti.

Cannot reproduce on 5960x CPU with 2.79a/b on Windows 7. Through author probably used their GTX 980 Ti.

Philipp Oeser commented

2018-04-30 11:41:07 +02:00

@ChristopherAnderssarian : thx for testing.
OSL is CPU only afaik.

@ChristopherAnderssarian : thx for testing. OSL is CPU only afaik.

ChristopherAnderssarian commented

2018-04-30 14:25:28 +02:00

dufff.....
Shows I don't have experience with GPU Rendering....

dufff..... Shows I don't have experience with GPU Rendering....

Tim commented

2018-04-30 17:17:55 +02:00

The full error message is:

LLVM ERROR: Cannot select: 0x18cf82f1080: f32 = X86ISD::FSETCCss 0x18cf82f79e0, 0x18cf82f1880, 0x18cf82f1280 [ORD=89] [ID=38]
  0x18cf82f79e0: f32 = X86ISD::FMIN 0x18cf82f81f0, 0x18cf82f1780 [ORD=87] [ID=37]
    0x18cf82f81f0: f32,ch = load 0x18cf348cc88, 0x18cf82f7ff0, 0x18cf34244f0<LD4[ConstantPool]> [ID=31]
      0x18cf82f7ff0: i64 = X86ISD::Wrapper 0x18cf34245f0 [ID=19]
        0x18cf34245f0: i64 = TargetConstantPool<float 1.000000e+00> 0 [ID=13]
      0x18cf34244f0: i64 = undef [ID=3]
    0x18cf82f1780: f32,ch = load 0x18cf348cc88, 0x18cf3422fd0, 0x18cf34244f0<LD4[%sunkaddr8]> [ORD=85] [ID=36]
      0x18cf3422fd0: i64 = add 0x18cf34231d0, 0x18cf3424af0 [ORD=83] [ID=30]
        0x18cf34231d0: i64,ch = CopyFromReg 0x18cf348cc88, 0x18cf82f70e0 [ORD=82] [ID=18]
          0x18cf82f70e0: i64 = Register %vreg3 [ID=1]
        0x18cf3424af0: i64 = Constant<8> [ID=2]
      0x18cf34244f0: i64 = undef [ID=3]
  0x18cf82f1880: f32 = ConstantFP<0.000000e+00> [ID=4]
  0x18cf82f1280: i8 = Constant<6> [ID=12]
In function: node_mix_0000018CBF9EAF70_10
Error: EXCEPTION_ACCESS_VIOLATION

Whether the script works or crashes seems to depend on what its output is connected to. I tested a few different cases, I can reproduce these results 100% of the time:

Crashes:
Output of the Script node connected to Fac of MixRGB node, when Color1 != Color2. (see: the attached .blend file in original post)
Output of the Script node connected to Fac of Mix Shader node.
Output of the Script node connected to Saturation of Hue/Saturation Node.

Works:
Output of the Script node connected to Fac of MixRGB node, when Color1 == Color2. (I guess the entire node is optimized away in this case?)
Output of the Script node connected to Strength of Emission node.
Output of the Script node connected to Hue of Hue/Saturation Node.

The full error message is: ``` LLVM ERROR: Cannot select: 0x18cf82f1080: f32 = X86ISD::FSETCCss 0x18cf82f79e0, 0x18cf82f1880, 0x18cf82f1280 [ORD=89] [ID=38] 0x18cf82f79e0: f32 = X86ISD::FMIN 0x18cf82f81f0, 0x18cf82f1780 [ORD=87] [ID=37] 0x18cf82f81f0: f32,ch = load 0x18cf348cc88, 0x18cf82f7ff0, 0x18cf34244f0<LD4[ConstantPool]> [ID=31] 0x18cf82f7ff0: i64 = X86ISD::Wrapper 0x18cf34245f0 [ID=19] 0x18cf34245f0: i64 = TargetConstantPool<float 1.000000e+00> 0 [ID=13] 0x18cf34244f0: i64 = undef [ID=3] 0x18cf82f1780: f32,ch = load 0x18cf348cc88, 0x18cf3422fd0, 0x18cf34244f0<LD4[%sunkaddr8]> [ORD=85] [ID=36] 0x18cf3422fd0: i64 = add 0x18cf34231d0, 0x18cf3424af0 [ORD=83] [ID=30] 0x18cf34231d0: i64,ch = CopyFromReg 0x18cf348cc88, 0x18cf82f70e0 [ORD=82] [ID=18] 0x18cf82f70e0: i64 = Register %vreg3 [ID=1] 0x18cf3424af0: i64 = Constant<8> [ID=2] 0x18cf34244f0: i64 = undef [ID=3] 0x18cf82f1880: f32 = ConstantFP<0.000000e+00> [ID=4] 0x18cf82f1280: i8 = Constant<6> [ID=12] In function: node_mix_0000018CBF9EAF70_10 Error: EXCEPTION_ACCESS_VIOLATION ``` Whether the script works or crashes seems to depend on what its output is connected to. I tested a few different cases, I can reproduce these results 100% of the time: Crashes: Output of the Script node connected to Fac of MixRGB node, when Color1 != Color2. (see: the attached .blend file in original post) Output of the Script node connected to Fac of Mix Shader node. Output of the Script node connected to Saturation of Hue/Saturation Node. Works: Output of the Script node connected to Fac of MixRGB node, when Color1 == Color2. (I guess the entire node is optimized away in this case?) Output of the Script node connected to Strength of Emission node. Output of the Script node connected to Hue of Hue/Saturation Node.

Ray molenkamp commented

2018-10-10 16:53:27 +02:00

Added subscriber: @LazyDodo