Cycles crushes with updating lights on GPU (Nvidia 1050) importing .obj #68016

New Issue

Arseny Popov · 2019-07-31T20:08:18+02:00

Arseny Popov commented

2019-07-31 20:08:18 +02:00

Good day to you. I am a noob, please don't judge. :) I have this problem with Cycles in new 2.80 release. Every single time when I import heavy mesh .obj

(lets say 500k verts) into the scene (1 mesh, camera , and environment texture, nothing more) I have this thing happening. On CPU it works perfectly fine,  let's say it takes 1800mb of memory, same as it was in 2.79. And in 2.79 when when you switch to GPU, memory  goes down to 800 and slowly goes back to 1800 and shows 950mb in render tab. and it works ok,  . IN this new 2.80 releace , when I'm adding environment texture to see how model looks like, AND go to GPU , pressing rendered view button,  when it comes to updating lights  RAM peaks to 5gb and it becomes extremely laggy, but I still can close Blender. IF I don't press rendered view and simply go F12 to render image , on "updating lights" computer completely freezes  (mouse not moving, clock not ticking) and nothing helps but  hard reset. BUT, IF I go 2.79, import same model .obj, same environment texture and save it as blender file, when I open it in new 2.80.75 it works completely ok on GPU and has no problems at all, and works really fast and actually usues less memory.  IF i do the same in 2.80.75, saving file before going to GPU , close blender, reopen it, switch to GPU,  it doen't crush but updating lights takes longer time and Cycles uses 1 GB more memory and viewport is much slower. So the worse bug only happens wnen you go import-->.obj.  Thank you.  {F7640015}

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.25

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: f6cb5f5449
Worked: (optional)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

Good day to you. I am a noob, please don't judge. :) I have this problem with Cycles in new 2.80 release. Every single time when I import heavy mesh .obj ``` (lets say 500k verts) into the scene (1 mesh, camera , and environment texture, nothing more) I have this thing happening. On CPU it works perfectly fine, let's say it takes 1800mb of memory, same as it was in 2.79. And in 2.79 when when you switch to GPU, memory goes down to 800 and slowly goes back to 1800 and shows 950mb in render tab. and it works ok, . IN this new 2.80 releace , when I'm adding environment texture to see how model looks like, AND go to GPU , pressing rendered view button, when it comes to updating lights RAM peaks to 5gb and it becomes extremely laggy, but I still can close Blender. IF I don't press rendered view and simply go F12 to render image , on "updating lights" computer completely freezes (mouse not moving, clock not ticking) and nothing helps but hard reset. BUT, IF I go 2.79, import same model .obj, same environment texture and save it as blender file, when I open it in new 2.80.75 it works completely ok on GPU and has no problems at all, and works really fast and actually usues less memory. IF i do the same in 2.80.75, saving file before going to GPU , close blender, reopen it, switch to GPU, it doen't crush but updating lights takes longer time and Cycles uses 1 GB more memory and viewport is much slower. So the worse bug only happens wnen you go import-->.obj. Thank you. {F7640015} ``` **System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1050/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 425.25 **Blender Version** Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: `f6cb5f5449` Worked: (optional) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]

Arseny Popov commented

2019-07-31 20:08:18 +02:00

Added subscriber: @Arseny-4

Gavin Scott commented

2019-07-31 22:19:30 +02:00

Added subscriber: @GavinScott

Gavin Scott commented

2019-07-31 22:19:30 +02:00

Is it possible for you to share the .blend file / .obj file?

Arseny Popov commented

2019-08-01 07:52:16 +02:00

test1.zip yes, here it is. Turns out the problem starts when you add environment texture. with 8k texture it works perfectly fine, but when you want to choose 16k , no matter HDR or not, it stucks with updating lights and freezing your computer, but if you do same thing in 2.79 and then open in 2.80 it has no problems.

[test1.zip](https://archive.blender.org/developer/F7640692/test1.zip) yes, here it is. Turns out the problem starts when you add environment texture. with 8k texture it works perfectly fine, but when you want to choose 16k , no matter HDR or not, it stucks with updating lights and freezing your computer, but if you do same thing in 2.79 and then open in 2.80 it has no problems.

Maciej Jutrzenka commented

2019-11-26 17:16:14 +01:00

Added subscriber: @MaciejJutrzenka