@Brendon Murphy (meta-androcto) Indeed this has been silently fixed somewhen, that's good news! Not sure when it has been adressed, but no crashes any longer

@Thomas Beck (plasmasolutions) I Just checked out the master Branch and patched it with the current version of this patch here (and a few others in addition, like the SurfaceFollow Modifier one). But I haven't changed any ifndef defines due to the total lack of C++ experience. I was only dealing with Python and C# so far.

FYI: Currently the patch fails to apply in three modules (tried applying in blender-v2.78b-release branch on commit c727bc7):

I meant this guide: http://www.gizmoplex.com/wordpress/compile-blender-as-python-module/

Just verified the suggestions. Using the raw Pyhton console made no difference, import errors would remain the same. But following the guide here **http://www.gizmoplex.com/wordpress/compile-blender-as-python-module/** (especially the part of copying the needed libs over to the Python35 directory) made it work. Can now successfully use the bpy build!

Thanks for your feedback,I will try your suggestions next Monday when I am back in the office.

@Bastien Montagne (mont29) HEAD BUMP You can close the report I guess. For one, the crash doesn't appear in newer Python versions, but further more my date format was nonsense. The formatter should have been:

@Vuk Gardašević (lijenstina) I've tested a version which I compiled on the 23rd of November (reports as 2.78.4), it crashes, but with some more latency. Testing VS2015 build, downloaded right now: WORKS! no crashes there!

Wasn't able to reply before as client projects kept me busy, sorry for the inconvenience.

would propose the following fixes:

Hi Sergey,

Maybe even skip the "named", as afaik unnamed objects don't exist in Blender. Otherwise people might ask how to name them...

@Julian Eisel (Severin) I tried to apply this as a patch today, but it failed for me (didn't find the lines to change). To I need to target a specific commit to make it work?

applying the patch currently fails, the kernel_types.h.rej file says:

accidentally created ot twice, please delete this one

Hi Bastien,

found this dirty hacky workaround here:

I'm working on a script that will add some additional input sockets to a node group based on output socket names from another node (input image) in the Compositor. This is the script so far:

strage quirks... man I sometimes hate my keyboard...

forgot to mention I am using the x64 Builds on two different machines, same behavior

I am having the same issue too. We made a lot of use in a recent project of the file output node and rendered the passes to OpenEXR MultiLayer. Not every output file crashed however, it was very hard to reproduce the error. However we were still able to do the compositing without problems by using Blender version 2.72 for Comp. That one never crashed.

same thing here, just one more thing: after confirming the "App has crashed" Windows Dialog, another line is added in the CMD Output:

The weird thing is that this only seems to affect the 64bit versions of Blender. I tested with 32bit Builds on the very same machine under the very same environment and it didn't crash. So even the nvidia driver is identical.

Hi Thomas,