Nodes in 2.70-RC2 and source build 211f08d extremely unstable (segfault crash) #39209

New Issue

Jean Ayer · 2014-03-16T01:30:02+01:00

Jean Ayer commented

2014-03-16 01:30:02 +01:00

System Information
Linux Mint 16 // GTX460 (nvidia drivers 334.21, also occurred in 331.38)
Reproduced by at least one other person on IRC

Blender Version
Broken: 2.70-RC2 2525f9c and source build 211f08d
Worked: 2.69.0 does not seem to crash from these steps

Short description of error
With a node material, typical material editing causes blender to crash instantly.
Crashes encountered with: adjusting Hardness, disabling a texture, connecting nodes, mousing over nodes

Exact steps for others to reproduce the error
Steps in attached .blend; basically just disable one texture or adjust material properties.
nodecrash-minimal-2.blend

Crash text
Blender 2.70 (sub 0), Commit date: 2014-03-15 16:37, Hash 211f08d
bpy.data.materials["nodemat"].use_textures- [x] = False # Property
bpy.data.materials["nodemat"].use_textures- [x] = True # Property

backtrace
./blender() [0x8d6f95]
/lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7eff99122ff0]
./blender(GPU_material_free+0x21) [0xfa98a1]
./blender(ED_render_id_flush_update+0x106) [0xb4c516]
./blender() [0xe83a9b]
./blender(DAG_ids_flush_tagged+0x97) [0xe84807]
./blender(BKE_scene_update_tagged+0x4f) [0xf3698f]
./blender(wm_event_do_notifiers+0x499) [0x8ddc89]
./blender(WM_main+0x20) [0x8d9000]
./blender(main+0xd7f) [0x8c2b1f]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7eff9910dde5]
./blender() [0x8d68f4]

**System Information** Linux Mint 16 // GTX460 (nvidia drivers 334.21, also occurred in 331.38) Reproduced by at least one other person on IRC **Blender Version** Broken: 2.70-RC2 2525f9c and source build 211f08d Worked: 2.69.0 does not seem to crash from these steps **Short description of error** With a node material, typical material editing causes blender to crash instantly. Crashes encountered with: adjusting Hardness, disabling a texture, connecting nodes, mousing over nodes **Exact steps for others to reproduce the error** Steps in attached .blend; basically just disable one texture or adjust material properties. [nodecrash-minimal-2.blend](https://archive.blender.org/developer/F81321/nodecrash-minimal-2.blend) **Crash text** Blender 2.70 (sub 0), Commit date: 2014-03-15 16:37, Hash 211f08d bpy.data.materials["nodemat"].use_textures- [x] = False # Property bpy.data.materials["nodemat"].use_textures- [x] = True # Property backtrace ./blender() [0x8d6f95] /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7eff99122ff0] ./blender(GPU_material_free+0x21) [0xfa98a1] ./blender(ED_render_id_flush_update+0x106) [0xb4c516] ./blender() [0xe83a9b] ./blender(DAG_ids_flush_tagged+0x97) [0xe84807] ./blender(BKE_scene_update_tagged+0x4f) [0xf3698f] ./blender(wm_event_do_notifiers+0x499) [0x8ddc89] ./blender(WM_main+0x20) [0x8d9000] ./blender(main+0xd7f) [0x8c2b1f] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7eff9910dde5] ./blender() [0x8d68f4]

Jean Ayer commented

2014-03-16 01:30:02 +01:00

Changed status to: 'Open'

Jean Ayer commented

2014-03-16 01:30:02 +01:00

Added subscriber: @vravCodyBurrow

Jean Ayer commented

2014-03-16 05:26:03 +01:00

Er, correction. Crash occurs in 2.69.0 as well. Cannot continue work on node-based material in the meantime.

Bastien Montagne commented

2014-03-16 08:26:17 +01:00

Added subscriber: @mont29

Bastien Montagne commented

2014-03-16 08:26:17 +01:00

Can’t reproduce this here (Debian 64 testing, ATI HD5730 +free driver)…

Just to be sure, are you using an "official" build from http://builder.blender.org/download/ ? If not, could you please try it?

Can’t reproduce this here (Debian 64 testing, ATI HD5730 +free driver)… Just to be sure, are you using an "official" build from http://builder.blender.org/download/ ? If not, could you please try it?

Jean Ayer commented

2014-03-16 10:39:50 +01:00

Yes, I tested with a build from buildbot as well as 2.7RC2 and 2.69 from the website. The crash occurs in all. 64bit, also. Did you adjust or enable/disable multiple times? It doesn't always occur the first time.

Bastien Montagne commented

2014-03-16 18:08:27 +01:00

Yep, I changed values at least several tens of times, without even a single little crash! ;) Even debug build with asan did not report any issue.

Now, iirc, we had other issues with ubuntu-like distros, which were LLVM conflicts related to graphic background of those distro…

But not sure at all this is the case here, backtrace does not really suggest this (though it happens in GPU Blender code).

Yep, I changed values at least several tens of times, without even a single little crash! ;) Even debug build with asan did not report any issue. Now, iirc, we had other issues with ubuntu-like distros, which were LLVM conflicts related to graphic background of those distro… But not sure at all this is the case here, backtrace does not really suggest this (though it happens in GPU Blender code).

lopata commented

2014-03-16 19:23:26 +01:00

Added subscriber: @lopataasdf

lopata commented

2014-03-16 19:23:26 +01:00

I confirm crash when change hardness value many times

nodecrash-minimal-2.crash.txt:

Blender 2.70 (sub 0), Commit date: 2014-03-14 22:47, Hash `2aff243`

bpy.data.materials["nodemat"].specular_hardness = 182 # Property

Win7 x64 blender-2.70-211f08d-win64-vc12

I confirm crash when change hardness value many times nodecrash-minimal-2.crash.txt: # Blender 2.70 (sub 0), Commit date: 2014-03-14 22:47, Hash 2aff243 bpy.data.materials["nodemat"].specular_hardness = 182 # Property Win7 x64 blender-2.70-211f08d-win64-vc12

lopata commented

2014-03-16 19:29:17 +01:00

Sorry, my version blender 2aff243

crashlog in Win7 x64 blender-2.70-211f08d-win64-vc12

Blender 2.70 (sub 0), Commit date: 2014-03-15 16:37, Hash `211f08d`

bpy.data.materials["nodemat"].specular_hardness = 240 # Property
bpy.data.materials["nodemat"].specular_hardness = 199 # Property
bpy.data.materials["nodemat"].specular_hardness = 185 # Property
bpy.data.materials["nodemat"].specular_hardness = 443 # Property
bpy.data.materials["nodemat"].specular_hardness = 100 # Property

Sorry, my version blender 2aff243 crashlog in Win7 x64 blender-2.70-211f08d-win64-vc12 # Blender 2.70 (sub 0), Commit date: 2014-03-15 16:37, Hash 211f08d bpy.data.materials["nodemat"].specular_hardness = 240 # Property bpy.data.materials["nodemat"].specular_hardness = 199 # Property bpy.data.materials["nodemat"].specular_hardness = 185 # Property bpy.data.materials["nodemat"].specular_hardness = 443 # Property bpy.data.materials["nodemat"].specular_hardness = 100 # Property

lopata commented

2014-03-16 19:49:12 +01:00

Blender do not crash when viewport in solid mode

Bastien Montagne commented

2014-03-16 20:59:43 +01:00

Well, still can’t reproduce it, but changing settings here is rather slow, so it might miss crash…

Two things you can test:

Start Blender with -t 1 option (to disable multi-threaded update), and see whether it still crash?
Switch 3DView to multitexture, and test again.

Well, still can’t reproduce it, but changing settings here is rather slow, so it might miss crash… Two things you can test: * Start Blender with `-t 1` option (to disable multi-threaded update), and see whether it still crash? * Switch 3DView to multitexture, and test again.

lopata commented

2014-03-16 21:43:36 +01:00

c:\Programs\Blender>blender.exe -t 1
Read new prefs: C:\Users\User\AppData\Roaming\Blender Foundation\Blender\2.70\co
nfig\userpref.blend
found bundled python: c:\Programs\Blender\2.70\python
read blend: C:\Temp\nodecrash-minimal-2.blend
Writing: C:\Users\User\AppData\Local\Temp\nodecrash-minimal-2.crash.txt
with multitexture not crash, but texture not displayed in viewport with this mode

1) c:\Programs\Blender>blender.exe -t 1 Read new prefs: C:\Users\User\AppData\Roaming\Blender Foundation\Blender\2.70\co nfig\userpref.blend found bundled python: c:\Programs\Blender\2.70\python read blend: C:\Temp\nodecrash-minimal-2.blend Writing: C:\Users\User\AppData\Local\Temp\nodecrash-minimal-2.crash.txt 2) with multitexture not crash, but texture not displayed in viewport with this mode

Jean Ayer commented

2014-03-16 21:46:09 +01:00

The -t 1 option doesn't change results, but switching to multitexture does. The viewport must be visible / in GLSL.

This might not be useful information but I also tested this in a VirtualBox machine running Arch+DWM (no desktop environment). Blender of course rasterizes very poorly and slowly in that environment, but I was unable to replicate the crash. Interesting that it happens in both Ubuntu and Windows desktop windowing environments. (On Mint I'm running LXDE after originally installing with KDE.)

edit: lopataasdf, thanks for also testing this :)

The `-t 1` option doesn't change results, but switching to multitexture does. The viewport must be visible / in GLSL. This might not be useful information but I also tested this in a VirtualBox machine running Arch+DWM (no desktop environment). Blender of course rasterizes very poorly and slowly in that environment, but I was unable to replicate the crash. Interesting that it happens in both Ubuntu and Windows desktop windowing environments. (On Mint I'm running LXDE after originally installing with KDE.) edit: lopataasdf, thanks for also testing this :)

Sergey Sharybin commented

2014-03-18 11:40:35 +01:00

Added subscriber: @Sergey

Sergey Sharybin commented

2014-03-18 11:40:35 +01:00

Blender 2.70 project should only contain bugs which are to be fixed for upcoming 2.70 release (aka, only regressions are to be added to this project).

Sergey Sharybin commented

2014-03-18 11:52:06 +01:00

Can not reproduce crash here (Debian 64 bit, 540m GPU) as well..

Lukas Tönne commented

2014-03-19 09:43:14 +01:00

Added subscriber: @LukasTonne

Lukas Tönne commented

2014-03-19 09:43:14 +01:00

Can't reproduce either (arch linux, GTX 660, driver 331.38)

Lukas Tönne self-assigned this 2014-03-21 12:29:22 +01:00

Lukas Tönne commented

2014-03-21 12:29:22 +01:00

Managed to reproduce with blender-softwaregl (thanks sergey). Seems to be a threading bug somehow, perhaps compounded by the horrible Material nesting in BI material nodes ...