Is anyone still getting a crash after changing ‘any’ setting in blender and then hitting render.
In my situation once blender crashes out due to the issue, every time I run blender after this (until I restart) gives me an instant crash upon hitting render.
I did read somewhere that it’s been fixed, but I don’t think it has, since it’s happening with the latest render branch I could find (1321_27747) and every other blender build I’ve tried.
If I’m the only person suffering this then I’ll put it down to something wrong with my set-up, if not I’ll submit a bug report and create an example file.
There were, maybe still are a number of bugs reported about using F12 with or without esc. Like hit F12. esc because the render settings need tweaking, then hitting F12 again caused a crash mainly on Windows, couldn’t get it to crash on Linux.
Rendering to a separate window seems to help a bit, but then I can’t use F11 to bring up the render window. Also, I have to always remember to close the render window instead of using ESC otherwise the focus doesn’t return the main Blender window. Pressing ESC seems to only adjust the render window’s z-order (puts it underneath the main window) but it remains the actively selected window. But, I seem to get fewer crashes when using the window output option. I can always get a first render, but oftentimes changing a setting in the World properties (especially things related to lighting) results in a crash. I’ve gotten into the habit of always saving before attempting to render.
I’m experiencing the same issue when changing some settings (especially on lights). I found that hitting F12 too soon after the changes crashes Blender, but if I wait for some seconds before rendering, everything’s okay.
I think this bug is related to a bad use of memory, Blender doesn’t have time to calculate changes if you render immediately after tweaking settings (although I have 4 Go of RAM on Windows 7)
Blender’s used to crash on me under the same conditions. The fix that worked for me was rendering to image editor instead of fullscreen. Since then, no crashes
i actually have the exact same problem. every time i save, then render immediately afterward, it crashes. it’s kinda annoying, but i’ve discovered that simply selecting something (or something else if something is already selected) before rendering usually removes the problem… it’s like Blender can’t handle the saving and rendering at the same time…
Hitting F12 can also turn into a crash here. It’s far less often with the latest builds, though. But i noticed it happens mostly if i didn’t gave any input about the target folder and the type of rendering (codec and compression).
-render to new window, not full screen
-after returning to the main blender window after rendering, I will click in a few areas in the main window or at least give it a couple of seconds before I hit F12 again.
-always save before rendering, habitual (hit F2, then Numpad++, then enter to save a file with an incremented number added, hard for me to explain but it’s a nice trick so save multiple backups for those who don’t know this keyboard shortcut.)
Another fix… wich isn’t really one:
turning off any cameras, lights, objects that aren’t needed in the final render.
I had again few crashes, lately, and wondered what was happening. I must agree that two heavy renderings where allready eating of quite much of the CPUs, but once the sole needed stuff remained in the third scene, it also rendered OK with no crash.
