Crash when changing material color in 3D view w/ Render enabled #34725
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
9 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#34725
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
%%%--- Windows 8 64bit, NVidia GTX 570---
I'm using the default .blend file with a cube, have also tested on other shapes with same results using Cycles.
I have tried this with Cuda disabled and enabled with the same resultant crash.
I have also used the official WHQL NVidia drivers and the two subsequent beta drivers NVidia has released. Under all drivers Blender 2.65a works correctly.
Open Blender, set Viewport Shading to: Rendered.
Go to Materials and choose Diffuse Color.
Move it around a few times to change the color - crash.
If I had to guess, I'd think this is a driver issue with NVidia - but, I can use 2.65a with any of the three NVidia drivers from 310.90 to 314.21 and Blender materials working perfectly while using Viewport Shading set to Rendered under Cycles. If this were purely a driver issue, then why does 2.65a work perfectly while all 2.66 versions (as far as I've tested) are not working - at least for me.
My work around is to simply use Material Shading.
%%%
Changed status to: 'Open'
%%%In 2.66a we added preview rendering in material buttons, can you check if that's the issue? Just make the preview panel hidden (close it with triangle).
Do note that Blender's code is cross platform and being used for linux/osx/windows successfully - somehow we get mostly reports like this for Windows 8, which is quite suspicious...
%%%
%%%So you are using GPU rendering with CUDA, not CPU rendering, is that correct?%%%
%%%Thomas, I have tried this with both GPU/CPU and the results are the same. But due to Ton's suggestion I can add more details.
Closing the preview window doesn't make a difference.
But these things do: set Viewport Shading to Rendered, go to Materials, click on Diffuse Color and slide around the color palette and I crash. If I do not 'Slide" my mouse over the palette but only choose a color with a single click, I don not "immediately" crash. Though I will crash after I do this 3 to 5 times.
I tried switching between Rendered and Solid between color changes and fairly consistently can do this 4 or 5 times, each time choosing a different color for the cube, and there is not crash. Each time I zoom in the rendered scene and can spin around the rendered object and there is no crash. Then about the 4th or 5th attempt to change the color - crash. It is the same whether the Material Preview window is open or not.%%%
%%%I tried it on Win 7 64 bit / Blender 2.66a. NVidia GT240. Both with Preview shown and not shown (collapsed).
No crash.
I have to agree with Ton here, it could be Win 8 related... maybe combination of driver and OS issues, and how Blender access it.
BTW, you've said 'files attached' but I don't see any.%%%
%%%Make sure you use driver 314.** or newer. I also can't confirm any crashers on Win 7 here. %%%
%%%I've tried drivers from 310.90 to the latest 314.21.
It may very well be a Windows 8 issue as I've also tested this on a Windows 8 laptop and am getting the same crash.
@Fable I for one did not in fact attach a file. While the crash occurs with any object or scene, one only needs to test on the default scene for the crash to happen.%%%
%%%A change has occurred with builder bot v2.66.4 r55562 - If I choose Viewport Shading: Rendered, I get (Cuda error; Out of memory in cuLaunchGrid(cuPathTrace, xblocks, yblocks). The viewport itself is cubed, as in it looks like an alpha background. There is no object in this view
Another thing, using CPU rendering and choosing different Diffuse colors, I can now select 8 to 10 color changes before crashing.
And earlier I had not pointed this out, but Viewport Shading set to Material with GPU rendering enabled has no problems.%%%
%%%--- Windows 7 64bit, 4GB RAM, NVidia Geforce 9500 GT (new driver)---
- Blender version with error: 2.66a and blender-2.66-r55587-win64.--- First time using cycles so i don't know if it works before...
Hi,
I have similar but really weird problem.
Problem: Blender crash when i am building/changing material (probably with anything) and have 3d vieport rendering enabled.
weird stuff: When i deleted subsurf and then add it again it didn't crash.
I am uploading both files in scifi.rar (i should rename that probably :) ). I tried simplified it as much as possible, but i was not able to replicate it from scratch.
To crash blender, just change color or energy in node tree couple times (1-2 second changing color and it crashed ...)%%%
%%%Using build bot r55891 now, problem described above still exists, and still on more than one installation.
New find: if I resize the Properties panel with Materials selected and Preview ON - I crash.
If I close the Preview panel first, I do not crash.%%%
%%%try using the viewport preview render from within the camera and enable border render (shift+B) for like 1/8th of the camera and try changing the colour.
If that doesn't crash its probably just an out of memory crash, so that your hardware cannot handle dealing with such a big scene at once without splitting it into tiles + making changes in realtime.%%%
%%%I haven't been able to redo any of these crashes myself. If you get crashes please always attach a .blend file, for example the preview panel is not open in the default startup.blend, and there may still be other subtle things that influence the crash.
I recently fixed a crash related to OSL (revision 55792), which might fix the crash in scifi.rar as that file has OSL enabled. I also just fixed another crash that may be related (revision 55991). So if anyone could confirm the crash in builds with revision 55991 or newer that would be helpful.%%%
%%%Hi Brecht,
I can confirm a crasher here now:
SVN 56005, Windows 7 x64, MSVC build, CPU rendering:
Note: this only happens with OSL enabled, when disabled I cannot trigger the crash. %%%
%%%I was able to reproduce on 2.66a distrobution release with OSL on 64bit intel Ubuntu 12.10 EVGA Titan, but as the previous poster only with OSL checked and I thought that was pretty much experimental and off limits for most part anyway? I just thought I'd chime in since it happened on linux, but again not very meaningful since it was using OSL.%%%
%%%OSL is neither experimental nor off limits. %%%
%%%Very good then, the reason I posted is to show that there was an issue with Ubuntu as well as Windows with OSL checked. %%%
%%%Committed a fix for OSL now that should avoid this crash. I'm not really sure though because it's difficult to redo it here, crash happens only rarely. Please test, and if it's not fixed I can reopen this report.%%%
Changed status from 'Open' to: 'Resolved'
%%%I have the same problem with Blender 2.66a on Ubuntu 12.10 / 64bit
uname -ra
Linux io 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25 19:58:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
VGA compatible controller: NVIDIA Corporation GF114 [GeForce GTX 560 Ti] (rev a1) (prog-if 00 [VGA controller])
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: GeForce GTX 560 Ti/PCIe/SSE2
OpenGL version string: 4.2.0 NVIDIA 304.88
OpenGL shading language version string: 4.20 NVIDIA via Cg compiler
Blender 2.66a downloaded from blender.org
Factory defaults - default cube.
Change viewport to Cycles render.
Select cube - go to materiel - defuse color - slide color selector around. On button release it crashes.
blender.crash.txt :
Blender 2.66 (sub 1), Revision: 55057
bpy.data.screens["Default"].(null) = 'RENDERED' # Property
backtrace
/home/jkp/Programs/blender/blender() [0xea6c1c]
/home/jkp/Programs/blender/blender() [0xea6e5a]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f70cccd34a0]
/home/jkp/Programs/blender/blender(_ZN3OSL3pvt26OSL_Dummy_JITMemoryManager17setMemoryWritableEv+0x7) [0xe8b077]
/home/jkp/Programs/blender/blender() [0x33dd39c]
/home/jkp/Programs/blender/blender() [0x343c5b2]
/home/jkp/Programs/blender/blender() [0x3b0063f]
/home/jkp/Programs/blender/blender() [0x3b00723]
/home/jkp/Programs/blender/blender() [0x3b00846]
/home/jkp/Programs/blender/blender() [0x33d8af7]
/home/jkp/Programs/blender/blender() [0x33d8e7f]
/home/jkp/Programs/blender/blender() [0x33d8fd9]
/home/jkp/Programs/blender/blender() [0xe8ab90]
/home/jkp/Programs/blender/blender(_ZN3OSL3pvt16RuntimeOptimizer14optimize_groupEv+0xb7c) [0xe4dfcc]
/home/jkp/Programs/blender/blender(_ZN3OSL3pvt17ShadingSystemImpl14optimize_groupERNS_18ShadingAttribStateERNS0_11ShaderGroupE+0x14a) [0xe4e90a]
/home/jkp/Programs/blender/blender(_ZN3OSL14ShadingContext7executeENS_3pvt9ShaderUseERNS_18ShadingAttribStateERNS_13ShaderGlobalsEb+0x186) [0xdfe636]
/home/jkp/Programs/blender/blender(_ZN3ccl9OSLShader15eval_backgroundEPNS_13KernelGlobalsEPNS_10ShaderDataEiNS_13ShaderContextE+0x4e) [0x19c6b4e]
/home/jkp/Programs/blender/blender() [0x1946adc]
/home/jkp/Programs/blender/blender() [0x194a47e]
/home/jkp/Programs/blender/blender(_ZN3ccl26kernel_cpu_sse3_path_traceEPNS_13KernelGlobalsEPfPjiiiii+0x1437) [0x19603b7]
/home/jkp/Programs/blender/blender(_ZN3ccl9CPUDevice17thread_path_traceERNS_10DeviceTaskE+0x19f) [0x1868e2f]
/home/jkp/Programs/blender/blender(_ZN3ccl13TaskScheduler10thread_runEi+0x28) [0x1850828]
/home/jkp/Programs/blender/blender(_ZN3ccl6thread3runEPv+0x18) [0x1850e78]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a) [0x7f70cd662e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d) [0x7f70ccd90ccd]
%%%
%%%That does indeed look like the same issue. The 2.67 test build has the fix:
http://download.blender.org/release/Blender2.67/%%%
%%%Unfortunately the RC1 of 2.67 gives the same problem (on the same machine)
jkp@io:~/Programs/blender-2.67-RC-linux-glibc211-x86_64$ cat /tmp/blender.crash.txt
Blender 2.66 (sub 6), Revision: 56271
bpy.data.screens["Default"].(null) = 'RENDERED' # Property
bpy.context.object.active_material.diffuse_color = (0.479657, 0.8, 0.705051) # Property
bpy.context.object.active_material.diffuse_color = (0.8, 0.297926, 0.507929) # Property
backtrace
./blender() [0xf24159]
./blender() [0xf24397]
/lib/x86_64-linux-gnu/libc.so.6(+0x364a0) [0x7f7353b594a0]
[0x7f733c71bca0]
%%%
%%%A quick test with 2.65a did not result in a crash.%%%
%%%Brecht,
Sorry about the late replay but I've been in Germany on family emergency. My problem with crashing I have just learned is not Blender itself, it is in my startup.blend file.
I cannot duplicate the error in 2.65 and if I start Blender 2.66 (most current buildbot and official release) with a fresh startup.blend file I do not get a crash condition while moving through the color picker. My apologies for not trying this sooner.
I am including a link to my startup.blend should you decide you'd like to try and find what is causing the condition as apparently I'm not the only one having this issue.
http://www.pasteall.org/blend/21131%%%