Change Details

{F8847210}**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `rB0330d1af29c0` Worked: 2.8x (did not have this issue wit versions < 2.9) **Short description of error** When rendering with Cycles and doing actions in parallel like changing Viewport Shading from "Material Preview" to "Rendered" (while using Cycles), or even only moving around the rendering window, Blender either freezes completely (but stoppable via Taskmanager) or crashes the whole machine. Symptoms are different. Sometimes screen flips between full black and full white. Sometimes it is possible to still access the Taskmanager, but in some cases also mouse freezes and only pressing the power button can bring the system up again. **Exact steps for others to reproduce the error** - Set Viewport Shading to "Material preview" - Press F12 to start rendering - Set Viewport Shading to "Rendered" - Move around the render window with the mouse Normally the issue is reproducible a after a view seconds. Sometimes its even enough just to press F12 and move the window. It looks like the issue does not happen that offen when I remove some of the textures (also attach in the zip), but it doesn't look like a specific texture causes the issue. Even when I'm able to stop the hanging/crashed Blender process it looks like something with the display driver is broken permanently after restarting Blender the issue is back immediately. When I then reboot the machine, it takes a little bit longer until I can reproduce it. I also saw the attached image of the menu (with a lot of green little dots). Minimizing/maximizing the Blender Window did not help in this case to restore the menus. My machine 0,5 years old thus a very new system with a Radeon RX570. I can't reproduce the issue with a simple cube (incl. a material). It also doesn't matter when changing the number of threads in use to a fixed number (lower than 12, which is the maximum of my CPU). In case I set it to a very low number e.g. 1-3 it even seems to get worse. The issue than appears nearly immediately. If you need additional information, let me know. I really love version 2.9 and the new features. Would be really great if you could find and fix this annoying issue or even let me know if there is a good workaround. Thanks & Regards, Bernd

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `rB0330d1af29c0` Worked: 2.8x (did not have this issue wit versions < 2.9) **Short description of error** When rendering with Cycles and doing actions in parallel like changing Viewport Shading from "Material Preview" to "Rendered" (while using Cycles), or even only moving around the rendering window, Blender either freezes completely (but stoppable via Taskmanager) or crashes the whole machine. Symptoms are different. Sometimes screen flips between full black and full white. Sometimes it is possible to still access the Taskmanager, but in some cases also mouse freezes and only pressing the power button can bring the system up again. **Exact steps for others to reproduce the error** - Set Viewport Shading to "Material preview" - Press F12 to start rendering - Set Viewport Shading to "Rendered" - Move around the render window with the mouse Normally the issue is reproducible a after a view seconds. Sometimes its even enough just to press F12 and move the window. It looks like the issue does not happen that offen when I remove some of the textures (also attach in the zip), but it doesn't look like a specific texture causes the issue. Even when I'm able to stop the hanging/crashed Blender process it looks like something with the display driver is broken permanently after restarting Blender the issue is back immediately. When I then reboot the machine, it takes a little bit longer until I can reproduce it. I also saw the attached image of the menu (with a lot of green little dots). Minimizing/maximizing the Blender Window did not help in this case to restore the menus. My machine 0,5 years old thus a very new system with a Radeon RX570. I can't reproduce the issue with a simple cube (incl. a material). It also doesn't matter when changing the number of threads in use to a fixed number (lower than 12, which is the maximum of my CPU). In case I set it to a very low number e.g. 1-3 it even seems to get worse. The issue than appears nearly immediately. If you need additional information, let me know. I really love version 2.9 and the new features. Would be really great if you could find and fix this annoying issue or even let me know if there is a good workaround. Thanks & Regards, Bernd {F8847210} {F8851693} {F8851694} {F8853610}

{F8847210}**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.2 26.20.15002.61 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `rB0330d1af29c0` Worked: 2.8x (did not have this issue wit versions < 2.9) **Short description of error** When rendering with Cycles and doing actions in parallel like changing Viewport Shading from "Material Preview" to "Rendered" (while using Cycles), or even only moving around the rendering window, Blender either freezes completely (but stoppable via Taskmanager) or crashes the whole machine. Symptoms are different. Sometimes screen flips between full black and full white. Sometimes it is possible to still access the Taskmanager, but in some cases also mouse freezes and only pressing the power button can bring the system up again. **Exact steps for others to reproduce the error** - Set Viewport Shading to "Material preview" - Press F12 to start rendering - Set Viewport Shading to "Rendered" - Move around the render window with the mouse Normally the issue is reproducible a after a view seconds. Sometimes its even enough just to press F12 and move the window. It looks like the issue does not happen that offen when I remove some of the textures (also attach in the zip), but it doesn't look like a specific texture causes the issue. Even when I'm able to stop the hanging/crashed Blender process it looks like something with the display driver is broken permanently after restarting Blender the issue is back immediately. When I then reboot the machine, it takes a little bit longer until I can reproduce it. I also saw the attached image of the menu (with a lot of green little dots). Minimizing/maximizing the Blender Window did not help in this case to restore the menus. My machine 0,5 years old thus a very new system with a Radeon RX570. I can't reproduce the issue with a simple cube (incl. a material). It also doesn't matter when changing the number of threads in use to a fixed number (lower than 12, which is the maximum of my CPU). In case I set it to a very low number e.g. 1-3 it even seems to get worse. The issue than appears nearly immediately. If you need additional information, let me know. I really love version 2.9 and the new features. Would be really great if you could find and fix this annoying issue or even let me know if there is a good workaround. Thanks & Regards, Bernd {F8847210} {F8851693} {F8851694} {F8853610}