Maniphest T82560

Crash on starting the render view or a render using cycles
Closed, Resolved

Assigned To
Philipp Oeser (lichtwerk)
Authored By
Liam Hanrahan (OuterCloudStudio)
Nov 10 2020, 2:18 AM
Tags
  • BF Blender
Subscribers
Ahmed H (nicaZe)
Liam Hanrahan (OuterCloudStudio)
Philipp Oeser (lichtwerk)
Robert Guetzkow (rjg)

Description

System Information
Operating system:Windows 10 64 bit
Graphics card: GTX 1060 (latest drivers. Tested on studio and game ready)

Blender Version
Broken: (2.19.1 Latest at the time)
Worked: no other version of blender I could find could open the file or render

Short description of error
when switching to rendered view by pressing z or hitting F12 to start a render blender closes.

Exact steps for others to reproduce the error
open the attached blend and start a render by f12{F9248897}

Event Timeline

Liam Hanrahan (OuterCloudStudio) created this task.Nov 10 2020, 2:18 AM
Ahmed H (nicaZe) added a subscriber: Ahmed H (nicaZe).EditedNov 10 2020, 4:34 AM

In your render properties before setting viewport into render view, assuming you are trying to render in cycles change your Device to GPU compute. This is if your edit > preferences > cycle render devices are also set to render using your GPU. I got mine working by setting my cycle render devices to OptiX, selecting the GPU I want to render with and then setting my render properties > Device, to GPU Compute.

Robert Guetzkow (rjg) changed the task status from Needs Triage to Needs Information from User.Nov 10 2020, 11:49 AM
Robert Guetzkow (rjg) added a subscriber: Robert Guetzkow (rjg).

The Blender version you've added to report is not correct. Did you mean 2.91.0 or 2.90.1? There was a bug in 2.90.1 (see T81116) which caused a crash when OptiX viewport denoising was enabled.

I can't reproduce a crash with the attached file. The file only contains a plane, a camera and a light, the render engine is set to Eevee. Is that the correct setup to reproduce the issue?

Please check if a current build of 2.91.0 or 2.92.0 works properly on your system. If it doesn't, then open Blender 2.92 installation directory and double click on the blender_debug_gpu.cmd. This will start Blender in debug mode and create log files. Try to make Blender crash again. Once it crashes the Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. Please also upload the crash log located in C:\Users\[your username]\AppData\Local\Temp\[project name].crash.txt (or simply type %TEMP% into the path bar of the Windows Explorer).

Liam Hanrahan (OuterCloudStudio) added a comment.Nov 10 2020, 2:25 PM

Sorry for the incorrect version, It was blender 2.90.1 which may be the bug you are talking about. It worked in the 2.91.0 Beta so thanks a lot!

Philipp Oeser (lichtwerk) closed this task as Resolved.Nov 10 2020, 2:30 PM
Philipp Oeser (lichtwerk) claimed this task.
Philipp Oeser (lichtwerk) added a subscriber: Philipp Oeser (lichtwerk).

Glad to hear, closing then!