Blender 2.7x OSL crash #39873

Closed
opened 2014-04-24 07:37:01 +02:00 by Einar · 16 comments

System Information
Windows 7 Ultimate 64bit
Corei7 3770
Quadro K4000
16GB RAM

Blender Version
Broken: 2.7a f93bc76

I start a new scene and enable Open Shading language feature, whenever I press render or switch to interactive rendering Blender crashes. I use CPU computing for rendering.
IMPORTANT NOTE: I installed Blender on other Windows 7 64bit computers which never had Blender installed and I get the same problem! OSL feature works fine on Windows XP!

Exact steps for others to reproduce the error

  1. I start a new scene
  2. Select Cycles render
  3. In render panel I enable Open Shading Language.
  4. Press render button or switch to material swatch preview or start interactive render.
  5. Blender crashes
**System Information** Windows 7 Ultimate 64bit Corei7 3770 Quadro K4000 16GB RAM **Blender Version** Broken: 2.7a f93bc76 I start a new scene and enable Open Shading language feature, whenever I press render or switch to interactive rendering Blender crashes. I use CPU computing for rendering. IMPORTANT NOTE: I installed Blender on other Windows 7 64bit computers which never had Blender installed and I get the same problem! OSL feature works fine on Windows XP! **Exact steps for others to reproduce the error** 1) I start a new scene 2) Select Cycles render 3) In render panel I enable Open Shading Language. 4) Press render button or switch to material swatch preview or start interactive render. 5) Blender crashes
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @MonteNero

Added subscriber: @MonteNero

Added subscriber: @mont29

Added subscriber: @mont29

Which build did you try, VC2008 or new VC2013? Also, could you please try one of our nightly builds?

Which build did you try, VC2008 or new VC2013? Also, could you please try one of our [nightly builds](http://builder.blender.org/download)?
Author

Hi,mont29!
I've just tried latest nightly build VS2013 for Windows7 64bit (blender-2.70-8cee587-win64-vc12.zip). Blender crashes anyway.
Regarding my older version 2.7a I don't know which VC it has. I just downloaded the package from official page.

Hi,mont29! I've just tried latest nightly build VS2013 for Windows7 64bit (blender-2.70-8cee587-win64-vc12.zip). Blender crashes anyway. Regarding my older version 2.7a I don't know which VC it has. I just downloaded the package from official page.

Added subscriber: @ThomasDinges

Added subscriber: @ThomasDinges

Will check this evening on Windows. Cannot confirm any issue on Mac OS now.

Will check this evening on Windows. Cannot confirm any issue on Mac OS now.

Added subscriber: @AtomP

Added subscriber: @AtomP

Can't confirm on my Windows 7 64bit using Blender 2.70a. Using nVidia driver version 335.23.

Can't confirm on my Windows 7 64bit using Blender 2.70a. Using nVidia driver version 335.23.

Cannot confirm on Windows 7 x64, MSVC 2008 11310b5

Must be something special on your configuration.

Cannot confirm on Windows 7 x64, MSVC 2008 11310b5 Must be something special on your configuration.
Author

Hhm. Is it possible that Blender crashes with curtain type of Windows version or service pack? Moreover I've got python 2.7 and Maya installed on the system, could they create a conflict?

Hhm. Is it possible that Blender crashes with curtain type of Windows version or service pack? Moreover I've got python 2.7 and Maya installed on the system, could they create a conflict?

Added subscriber: @JNMeiun

Added subscriber: @JNMeiun

cant enable OSL at all when in render view or rendering. tried multiple builds. x64 builds all crashed immediately even with no materials. the official win32 build is fine until a material node is connected with a material output. then it crashes.

<!> event has invalid window

this is all that showed up in console. it also seems to throw errors if you accidentally connect say a shader node to the fac input of a ramp. did that on accident because of messy organization of nodes. it crashed it like connecting a shader node to output with this.

Cycles shader graph connect: can only connect closure to closure (bsdf.BSDF to r
gb_ramp.Fac).

w7 x64, also have maya installed and the remnants of c4d.

of course that's a dumb thing to do and it wasnt intentional but that shouldn't crash blender.

edit: ps cant use osl with anything after 2.66. the default cube takes longer to crash. just guessing it seems to be something with updating the material preview.

being in anything other than the materials menu when connecting the node reliably gives some extra time before crashing. less complex materials reliably give a few seconds more before a crash. moderately complex geometry and more complex materials crash almost instantly.

anyone else want to try to replicate any of this? is it just on this end or are other people getting the same?

woops is this double posting on edit? it looks like it.

cant enable OSL at all when in render view or rendering. tried multiple builds. x64 builds all crashed immediately even with no materials. the official win32 build is fine until a material node is connected with a material output. then it crashes. ``` <!> event has invalid window ``` this is all that showed up in console. it also seems to throw errors if you accidentally connect say a shader node to the fac input of a ramp. did that on accident because of messy organization of nodes. it crashed it like connecting a shader node to output with this. ``` Cycles shader graph connect: can only connect closure to closure (bsdf.BSDF to r gb_ramp.Fac). ``` w7 x64, also have maya installed and the remnants of c4d. of course that's a dumb thing to do and it wasnt intentional but that shouldn't crash blender. edit: ps cant use osl with anything after 2.66. the default cube takes longer to crash. just guessing it seems to be something with updating the material preview. being in anything other than the materials menu when connecting the node reliably gives some extra time before crashing. less complex materials reliably give a few seconds more before a crash. moderately complex geometry and more complex materials crash almost instantly. anyone else want to try to replicate any of this? is it just on this end or are other people getting the same? woops is this double posting on edit? it looks like it.

Added subscriber: @willi-2

Added subscriber: @willi-2

Can't repro on Win7/64 with any blend file. (Also not inside VM on WinXP/32.)

Can't repro on Win7/64 with any blend file. (Also not inside VM on WinXP/32.)

Tested to see if it was OS configuration or specific to a service pack or update. It doesn't seem to be service pack specific, a bare bones install of 6.1 sp1 did nothing for it.Howevera complete install of 6.1SP1 and all of its** associated updates **resulted in a working OSL option.

Would MonteNero be willing to try to update to SP1 or SP2 to confirm? Or if already on SP1 try going through one of the windows 6.1 updates to see if one fixes the problem.

Tested to see if it was OS configuration or specific to a service pack or update. It doesn't seem to be service pack specific, a bare bones install of 6.1 sp1 did nothing for it.**However**a complete install of 6.1SP1 and all of its** *associated updates* **resulted in a working OSL option. Would MonteNero be willing to try to update to SP1 or SP2 to confirm? Or if already on SP1 try going through one of the windows 6.1 updates to see if one fixes the problem.
Sign in to join this conversation.
6 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: blender/blender#39873
No description provided.