Page MenuHome

Crash under cycles rendering using F12
Closed, ResolvedPublic

Description

System Information
win 7 x64

Blender Version
Broken: blender-2.74-Hash: 3bffcc6

Worked: blender-2.74- Hash: 9b99786

Short description of error
DESCRIPTION AND STEPS ----->>>https://youtu.be/khIN2UbcnZw

Blender crashes when F12 its use to render but rendering from the interface it works fine. The other thing is that i only was able to reproduce the crash using that object with that armature, if you remove the armature from the object it also renders ok. . .

To sum up, the leg object+armature modifier+F12 to render = crash
if any of the previous variables are remove it works ok.

Exact steps for others to reproduce the error
1- open


2- USE F12 to render
3- if it not crash move a bit the viewport and try again.

how to avoid crash
A
1- open


2- Use the render button on the properties panel to render a frame.
B
1-open
2-select the object "PIERNAS"
3- remove modifiers
4- render using f12 or interface button, it shouldn´t crash

NOTE: 1-I also try using the gooseberry version from buildbot and also crashes, ill try again with the next version of tomorrow Sunday.
NOTE: 2-I did that video to try to explain a bit better the problem, not sure if it possible to reproduce the bug under different circumstances i did the best i could to get the simplest sample of the file, even removing the materials reduce the percentage of crashes but still crashes though, the two only things that avoid crashes are, render from the interface or removing the armature modifier.

Event Timeline

Nahuel Belich (belich) raised the priority of this task from to 90.
Nahuel Belich (belich) updated the task description. (Show Details)
Nahuel Belich (belich) edited a custom field.

I cannot reproduce the crash at all here (linux64, using both release and debug builds)…

Cannot reproduce it eiter, Windows x64, 8dd055c

Thomas Dinges (dingto) lowered the priority of this task from 90 to 30.Apr 26 2015, 12:02 PM

Marking as incomplete now, we need a way to reproduce this.

Bastien Montagne (mont29) raised the priority of this task from 30 to Normal.Apr 26 2015, 12:02 PM

Switching to unconfirmed, thanks for the report but if no dev is able to reproduce it within two weeks we'll have to close it…

thanks for testing
i just downloaded both 32 and 64 version of the las build blender-2.74-3bffcc6 for windows, both still crash the same way, actually now also crash rendering using the button in the interface(but using the interface its a really random crash), so the deal must be among the object and the armature, removing the armature worked really well for me in my tests, maybe its on the material, i leave the material because removing it didn`t fully stabilized the render but made the crashes more random.

I also managed to get a laptop to test on other computer using this lastest builds,
WIn 7 home starter x86 32
Amd E-450 APU
same crash.

Yesterday i also try to test it under ubuntu 14.04 booting from a pendrive but when i try to uncompress the files downloaded from builder.blender.org it returns some corrupted files and when i try to uncompress under ubuntu unity also pops an error, something about linked libraries. . . :\ not sure. So a wasn´t able to properly test the bug under linux.

after two more hours testing, i had reduce the sample file down to a single case

the broken egg.

1- Open that file on a windows os using the latest build hash: bc160d8 or "3524676036c370822344f1c80b191d34644b3745"
2- f12 to render
3- crash

this simple file its done using an sphere with a armature and a subdivision surface modifier, and render from a maximize area (shift+spacebar)

i share this at irc blendercoders and gaia confirm the bug, also said that -"when i press F12 then i get an exception and in visual studio i see this stacktrace: http://www.pasteall.org/58065"-

(probably the title of the report its a bit misleading now)

Thomas Dinges (dingto) triaged this task as 50 priority.Apr 26 2015, 2:46 PM

Can confirm crash with egg_crash file on Windows x64.

Seems to be windows specific issue, still cannot reproduce the issue on linux, even with an asan build.

Only glitch I have is a 'noisy' image before first tile is rendered, as if we were reading uninitialized mem or so…