- User Since
- Oct 2 2014, 3:13 PM (120 w, 14 h)
There's very little to go on here, try using something like process monitor ( https://technet.microsoft.com/en-us/sysinternals/processmonitor.aspx ) to see what's going on.
Wed, Jan 18
This issue has been reported before, and the good news is: fixed! You can grab a build from http://builder.blender.org if you want it right now, or wait till the next release which will include this fix.
Tue, Jan 17
ng.outputs.new("NodeSocketColor", "color") ng.inputs.new("NodeSocketShader", "shader")
will probably work.
Sun, Jan 15
mont29, thread gets created here
Good news! This issue is already fixed! If you want the fix head over to https://builder.blender.org/download/ and grab a nightly, otherwise this will be fix in the next official version!
Sat, Jan 14
Tried 2.78a on 32 bit windows 10 also unable to reproduce....
Fri, Jan 13
In all fairness asking for a .blend is not a form victim blaming, sometimes it's just easier to reproduce a problem that way, what's always happening to you, might not happen to us, I just tried to reproduce this report, rendered my default cube, Full Sample on, off, didn't matter, rendered with no problem. messed 5 minutes with various options trying to trigger it , couldn't make it happen, Now if I had a .blend that would have crashed as soon as I hit render, I could have spend that time actually fixing the problem. So it's not a 'we don't believe you! prove it!' it's more of a 'help us to help you'
Can't repro either, please upload a sample blend, so all we have to do to trigger the crash is enable dupli verticles?
Can you try forcing vsync on for blender in the nvidia settings?
Mon, Jan 9
Not sure why, file is bigger now, but still missing textures,still the wrong layer selected and still no crashing behavior.. please resist changing the priority your self, it's easier for us if we manage that.
Sun, Jan 8
The sample file is missing some textures (be sure to use file->external data->pack into blend before uploading) , also there's nothing to render on the layer selected? When changing to the first or second layer, it renders fine with both 2.77 and 2.78a. Please provide a better test case.
Sat, Jan 7
this is a known issue, good news: it's fixed already! Pick up a build from builder.blender.org and you'll be allright!
Yup, that's TDR in action :) If you still want to render with a larger tile size here's how to change or disable the timeout value (but naturally anything you do is at your own risk)
mon29 you know the relink code better than anyone else, mind taking a peek here?
Thu, Jan 5
Can't repro either, but given the scene is very slow to render, i'm guessing he hit the TDR timeout on his gfx driver, try rending with a smaller tile size.
Yeah not much we can do about this, get more ram is my best advise.
Tue, Jan 3
added brackets to one-liners that needed it.
changed fmax to fmaxf some compilers did not have the float overload for fmax and caused a compile error.
Mon, Jan 2
Updated codesyle with feedback and fixed the gsgl shader with dingto's tip
Sun, Dec 25
please don't triage your self.
Sat, Dec 24
closed by committing rB3a9c490531556c1bad6e1f6e8cd7cd7f026b8437
Fri, Dec 23
Helped out on irc, but just for future reference, "bf_draw wasn't added to the SETUP_BLENDER_SORTED_LIBS macro in buildfiles/cmake/macros.cmake"
Dec 19 2016
Your sample file renders fine here, what exact steps need to be done to make blender crash with this file?
It got updated after 2.78a got released, try a nightly from builder.blender.org
Dec 17 2016
Update: With this fix and D2367 applied , x86/2015 passes all of our tests tests.
Dec 15 2016
This is fixed already, please try a nightly build from https://builder.blender.org/download/
I'm open for an alternative for the monstrosity that is the python path, it's the only way i found that supported both the release and debug version on windows, while also not breaking on linux.
Dec 13 2016
Dec 12 2016
@Kévin Dietrich (kevindietrich) Tricky one to reproduce, there's some subtlety to it. I can repro the bug but only if import the .abc file with 2.78a .
While running sanity checks before committing this diff, more problems showed up
Dec 9 2016
Duplicate of T49899
Dec 7 2016
Simulation just takes a long time, just let it run for a few hours.
I've been asked to land this one, (fine, easy work) however changes have been done since the patch has been accepted, @Sergey Sharybin (sergey) do you want to take one final look?
@Sergey Sharybin (sergey) / @Martijn Berger (juicyfruit) i've been asked to land this one (which is fine, easy work), however given the review process has been kinda stale on this one, I'd like you to take a look and mark it as accepted (or rejected and request changes) before it moves forward.
Duplicate of T50197
I'm also unsuccessful full in reproducing this one. Why is this tagged windows? original report came in on Linux 64 Debian Jessie ?
Fixed in last weekends lib upgrade.
Here's a stack trace
# Blender 2.78 (sub 4), Commit date: 2016-12-05 10:36, Hash 60dae91 bpy.context.area.type = 'TEXT_EDITOR' # Property bpy.ops.text.run_script() # Operator Python script fail, look in the console for now... # Error bpy.context.area.type = 'CONSOLE' # Property
Dec 6 2016
not my area of expertise, but by the looks of it, the Mesh Cache is an operator for reading a cache, not writing it (it needs an pc2 or mdd file), so if you're telling it to read a directory as an input file, the permission denied isn't that strange.
Not an area I frequently use, and couldn't figure it out based on your ticket.
Dec 4 2016
Updated libs to python 3.5.2 , issue remains on the vc2013 builds, the crash is coming out of the ms c runtime though, not sure what we could do about it, it's pretty much how wcsftime deals with a bad formatter, best advise is not to use a bad formatter.
Use a different build. Just the experimental 2015 x86 build has this issue.
Dec 3 2016
Dec 2 2016
Still, would be nice if we handled a failing allocation a little better than just crashing the process. I asked him to make this ticket so i could look at it.
I'm in the process of upgrading the windows libs, unless something unexpected causes issues the 3.5.2 libs should be available in the next few days.
Dec 1 2016
Hard to say what's wrong without looking at the files. Also please attach files to the report in the future, not on external hosting.
alembic has a legacy internal format called hdf5 which this file uses, blender currently does not support this legacy format.
the new msi installers indeed do not create those registry keys (as it is an artifact of the nsis (un)installer) they do however still register the .blend filetype handler, which you can use to track down the path of the blender installation. You can find this registry key at
Resolved in 2.78a
Nov 29 2016
32 bit windows by any chance? if so try a nightly
Nov 28 2016
It would, BlenderSession::builtin_image_info would query the PD settings once, to get the resolution, and beyond that the buffer dimensions would be passed down, so there's no need for rna_ShaderNodePointDensity_density_calc to query the PD Settings and get a potentially different answer.
Ideally i'd like to extend builtin_image_float_pixels_cb and builtin_image_pixels_cb to include the buffer dimensions (passing a pointer to a buffer, without telling the callee what size it is, just seems bad faith to me, and inviting issues like these) however that in turn causes a change to rna_ShaderNodePointDensity_density_calc (to include the buffer dimensions there as well) but that might be a breaking api change, not sure if that's ok? (doesn't look like any python is calling it though, so it just be a c/c++ code change)
race condition, in between the time ImageManager allocates ram for the texture and the time it gets sampled the ui managed to get in a change to the resolution. causing things to overflow in point_density_sample_func. Not quite sure how to stop that from happening. @Sergey Sharybin (sergey) any hints/tips?
Nov 27 2016
This one was easy to repro, point_density.blend
Can't seem to repro, added some loopcuts to cylinder.000, seemed just peachy, could be a driver bug.
Try running in software-gl mode (there should be a script in your blender folder for that) if that works, it's most likely a gpu driver issue, you could try changing the selection setting in UserPreferences->System->Selection and see if that improves things.
Nov 26 2016
32 bit windows by any chance? if so try a nightly should already be fixed.
Fairly sure this one is already fixed, try a nightly build
Nov 25 2016
Nov 24 2016
blender -b test.blend -o //file -F JPEG -x 1 -a --debug-cycles
for a couple of hundred frames, didn't seem to trigger the error, how often does this error occur for you?