Blender Crashes when using 3D view set to RENDER and getmessage ("trace", "geom:name", nameStr); called in OSL #38900

New Issue

Dylan Whiteman · 2014-03-01T06:33:08+01:00

Dylan Whiteman commented

2014-03-01 06:33:08 +01:00

System Information
Dell Inspiron 64bit
Windows 7

renderer: 'Intel(R) HD Graphics 4000'
vendor: 'Intel'
version: '4.0.0 - Build 9.17.10.2867'

Blender Version
Broken:
version 2.69 (sub 11), branch b'master', commit date b'2014-02-20' b'05:32', hash b'4789793', b'Release'
build date: b'2014-02-20', b'14:08:49'

Previous releases (2.69, 2.68 etc) crashed too.
Worked: (optional)

Blender crashes when trying to use the geom:name parameter in getmesage:

  getmessage ("trace", "geom:name", nameStr) 
  // If the line below is commented out, Blender does not crash.
  if (nameStr == "Cube") outcol = BLUE;

It will also crash if the "geom:name" parameter is changed to any of the other allowable strings.

Sample crash File:
http://www.pasteall.org/blend/27162

oslCrash01.blend

Exact steps for others to reproduce the error
To see the crash:
If you have downloaded "OSL_Crash01.blend": 1) Set the 3D VIEWPORT Shading setting to "RENDERED"
Blender will crash on a Windows 64bit machine.
Commenting out the line: if (nameStr == "Cube") outcol = BLUE;
below will allow the script to run.
If you just have this script source then, to see the crash: 1) Enamble OSL in Blender
2) Compile this script in the Blender text editor 3) Create a 3D mesh in Blender (e.g. the default cube)
4) Assign a new Cycles material to the new mesh. 5) Add a Script node to the new material and select this "osl_crash01.osl" script as the OSL script.
6) Connect the shaderOut node of hte script to the Material Output 7) Set the 3D VIEWPORT Shading setting to "RENDERED"
// Blender will crash on a Windows 64bit machine.

Thankyou for your help - and your work on this amazing system.

Cheers

Dylan

**System Information** Dell Inspiron 64bit Windows 7 renderer: 'Intel(R) HD Graphics 4000' vendor: 'Intel' version: '4.0.0 - Build 9.17.10.2867' **Blender Version** Broken: version 2.69 (sub 11), branch b'master', commit date b'2014-02-20' b'05:32', hash b'4789793', b'Release' build date: b'2014-02-20', b'14:08:49' Previous releases (2.69, 2.68 etc) crashed too. Worked: (optional) Blender crashes when trying to use the geom:name parameter in getmesage: ``` getmessage ("trace", "geom:name", nameStr) // If the line below is commented out, Blender does not crash. if (nameStr == "Cube") outcol = BLUE; ``` It will also crash if the "geom:name" parameter is changed to any of the other allowable strings. Sample crash File: http://www.pasteall.org/blend/27162 [oslCrash01.blend](https://archive.blender.org/developer/F79320/oslCrash01.blend) **Exact steps for others to reproduce the error** *To see the crash:* *If you have downloaded "OSL_Crash01.blend":* 1) Set the 3D VIEWPORT Shading setting to "RENDERED" *Blender will crash on a Windows 64bit machine.* *Commenting out the line:* if (nameStr == "Cube") outcol = BLUE; *below will allow the script to run.* *If you just have this script source then, to see the crash:* 1) Enamble OSL in Blender *2) Compile this script in the Blender text editor* 3) Create a 3D mesh in Blender (e.g. the default cube) *4) Assign a new Cycles material to the new mesh.* 5) Add a Script node to the new material and select this "osl_crash01.osl" script as the OSL script. *6) Connect the shaderOut node of hte script to the Material Output* 7) Set the 3D VIEWPORT Shading setting to "RENDERED" // Blender will crash on a Windows 64bit machine. Thankyou for your help - and your work on this amazing system. Cheers Dylan

Dylan Whiteman commented

2014-03-01 06:33:08 +01:00

Changed status to: 'Open'

Dylan Whiteman commented

2014-03-01 06:33:08 +01:00

Added subscriber: @DylanWhiteman

Lukas Tönne commented

2014-03-01 09:40:16 +01:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2014-03-01 09:40:16 +01:00

I'm pretty sure this is a bug in OSL ...

I'm getting the same on 64bit arch linux running OSL 1.3.3. Latest OSL release is 1.5.5, they seem to have fixed quite a bunch of bugs relating to getmessage:

https://github.com/imageworks/OpenShadingLanguage/blob/master/CHANGES

We should consider upgrading after the Blender 2.70 release ...

I'm pretty sure this is a bug in OSL ... I'm getting the same on 64bit arch linux running OSL 1.3.3. Latest OSL release is 1.5.5, they seem to have fixed quite a bunch of bugs relating to `getmessage`: https://github.com/imageworks/OpenShadingLanguage/blob/master/CHANGES We should consider upgrading after the Blender 2.70 release ...

Brecht Van Lommel was assigned by Lukas Tönne

2014-03-01 09:59:20 +01:00

blender-admin commented

2014-03-01 14:58:05 +01:00

This issue was referenced by blender/blender-addons-contrib@3eabe064ab

This issue was referenced by blender/blender-addons-contrib@3eabe064ab5401b9f0267c0a4a31379541084610

blender-admin commented

2014-03-01 14:58:05 +01:00

This issue was referenced by 3eabe064ab

This issue was referenced by 3eabe064ab5401b9f0267c0a4a31379541084610

Brecht Van Lommel commented

2014-03-01 14:58:40 +01:00