Cycles Render - Textures Disappear then Crashes the Render #89747

New Issue

Sienna Fuegonasus · 2021-07-09T02:38:23+02:00

Sienna Fuegonasus commented

2021-07-09 02:38:23 +02:00

System Information

Operating system: Windows 10
Graphics card: RTX 3090
CPU: 5900x
RAM: 64GB

Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44
version: 3.2.0 Alpha, branch: master, commit date: 2022-02-15 21:20, hash: `rBd3b1cce4000b`

Blender Version
Broken: 2.93
Broken: 3.1
Broken: 3.2

Short description of error
If I render this scene, the textures eventually start disappearing and turning pink then it crashes.
At first it renders the output just fine but eventually textures start disappearing then it crashes

Exact steps for others to reproduce the error
Render the blend file above as an animation and it should start producing errors and crash at around frame 240.

ErrorTestRoom_Smallester.rar

One thing I noticed was this in the console (on every frame):

Invalid graphics context in cuGraphicsUnregisterResource(cu_graphics_resource_) (intern/cycles/device/cuda/graphics_interop.cpp:36)

That message is the same as in #95651 (GPU error (Invalid graphics context in cuGraphicsUnregisterResource)), these might have the same underlying root cause, guess #render_cycles devs will need to check that

Then on the last frames rendered I get this:

E0216 13:47:06.263782 225559 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory
E0216 13:47:06.264526 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
E0216 13:47:12.915915 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0240.png'
 Time: 00:07.95 (Saving: 00:00.02)

E0216 13:47:14.160032 225594 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory
E0216 13:47:14.160919 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
E0216 13:47:20.773739 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0241.png'
 Time: 00:07.85 (Saving: 00:00.01)

E0216 13:47:22.079187 225606 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory
E0216 13:47:22.081022 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
E0216 13:47:28.747159 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0242.png'
 Time: 00:07.97 (Saving: 00:00.01)

Failed to create CUDA context (Operating system)

Refer to the Cycles GPU rendering documentation for possible solutions:
https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html

Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26)
Invalid context in cuStreamCreate(&cuda_stream_, CU_STREAM_NON_BLOCKING) (intern/cycles/device/cuda/queue.cpp:33)
Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31)
Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26)
Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31)
Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26)
Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31)
Invalid value in cuCtxDestroy_v2(cuContext) (intern/cycles/device/cuda/device_impl.cpp:138)
No device available to denoise on

Refer to the Cycles GPU rendering documentation for possible solutions:
https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html

Error: No device available to denoise on

Original report

Blend File and Textures Here (650MB)

How it's supposed to render

In the last few frames it renders with glitched out textures:

https://i.imgur.com/vNoCk39.png
https://i.imgur.com/fj1tqif.png
https://i.imgur.com/xKdk8vA.png
https://i.imgur.com/ErTXneV.png

Then it crashes.

Full render output here

Smaller File Size:

Smaller size file sample (180MB)

Even with less textures the error still happens.

This is how the render is supposed to look

Then last few frames it renders:

https://i.imgur.com/X3nhTh5.png
https://i.imgur.com/4UFJUYH.png
https://i.imgur.com/8v5Fvgc.png
https://i.imgur.com/LTfk5hY.png

Full render output here

Even more smaller rar file samples:

74MB
28MB
13MB

I won't repeat the description above, essentially same results even with less and less textures involved in the blend file. First 2 crash in the 80-90 frame range, smallest (13MB) crashes at around frame 130. No errors occur when there are no textures.

Exact steps for others to reproduce the error
Render the blend file above as an animation and it should start producing errors and crash at around frame 80-90.

Extra Notes
I've tried both OPTIX and CUDA and GPU only and GPU+CPU rendering and it produces the same error. CPU only rendering produces same error.

Rendering the blend in 2.92 produces the same error.

This does not happen when rendered in Eevee.

If I start the render in the frames that it glitches out on it renders the frame without error.

Rendering with "Persistent Data" option on fixes the issue but I'm not sure if it's a real fix.

**System Information** ``` Operating system: Windows 10 Graphics card: RTX 3090 CPU: 5900x RAM: 64GB ``` ``` Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 version: 3.2.0 Alpha, branch: master, commit date: 2022-02-15 21:20, hash: `rBd3b1cce4000b` ``` **Blender Version** Broken: 2.93 Broken: 3.1 Broken: 3.2 **Short description of error** If I render this scene, the textures eventually start disappearing and turning pink then it crashes. At first it renders the output just fine but eventually textures start disappearing then it crashes **Exact steps for others to reproduce the error** Render the blend file above as an animation and it should start producing errors and crash at around frame 240. [ErrorTestRoom_Smallester.rar](https://archive.blender.org/developer/F10218017/ErrorTestRoom_Smallester.rar) One thing I noticed was this in the console (on every frame): ``` Invalid graphics context in cuGraphicsUnregisterResource(cu_graphics_resource_) (intern/cycles/device/cuda/graphics_interop.cpp:36) ``` That message is the same as in #95651 (GPU error (Invalid graphics context in cuGraphicsUnregisterResource)), these might have the same underlying root cause, guess #render_cycles devs will need to check that Then on the last frames rendered I get this: ``` E0216 13:47:06.263782 225559 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory E0216 13:47:06.264526 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. E0216 13:47:12.915915 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0240.png' Time: 00:07.95 (Saving: 00:00.02) E0216 13:47:14.160032 225594 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory E0216 13:47:14.160919 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. E0216 13:47:20.773739 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0241.png' Time: 00:07.85 (Saving: 00:00.01) E0216 13:47:22.079187 225606 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory E0216 13:47:22.081022 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. E0216 13:47:28.747159 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0242.png' Time: 00:07.97 (Saving: 00:00.01) Failed to create CUDA context (Operating system) Refer to the Cycles GPU rendering documentation for possible solutions: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26) Invalid context in cuStreamCreate(&cuda_stream_, CU_STREAM_NON_BLOCKING) (intern/cycles/device/cuda/queue.cpp:33) Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31) Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26) Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31) Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26) Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31) Invalid value in cuCtxDestroy_v2(cuContext) (intern/cycles/device/cuda/device_impl.cpp:138) No device available to denoise on Refer to the Cycles GPU rendering documentation for possible solutions: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html Error: No device available to denoise on ``` **Original report** [Blend File and Textures Here ](https://www.dropbox.com/s/01rme2kblfqvmfd/ErrorTestRoom.rar?dl=0) (650MB) [How it's supposed to render ](https://i.imgur.com/YihtW91.png) In the last few frames it renders with glitched out textures: https://i.imgur.com/vNoCk39.png https://i.imgur.com/fj1tqif.png https://i.imgur.com/xKdk8vA.png https://i.imgur.com/ErTXneV.png Then it crashes. [Full render output here ](https://www.dropbox.com/s/rdktepyvgtsq8tj/TestRender.rar?dl=0) Smaller File Size: [Smaller size file sample ](https://www.dropbox.com/s/hndez7x2com4tph/ErrorTestRoom_Smaller.rar?dl=0) (180MB) Even with less textures the error still happens. [This is how the render is supposed to look ](https://i.imgur.com/QQY24Hv.png) Then last few frames it renders: https://i.imgur.com/X3nhTh5.png https://i.imgur.com/4UFJUYH.png https://i.imgur.com/8v5Fvgc.png https://i.imgur.com/LTfk5hY.png [Full render output here ](https://www.dropbox.com/s/u4kszx2jzwhch9k/TestRender2.rar?dl=0) Even more smaller rar file samples: [74MB ](https://www.dropbox.com/s/57ihx0t5u54vgwj/ErrorTestRoom_Smallerer.rar?dl=0) [28MB ](https://www.dropbox.com/s/f2ng1b3gwkumbt2/ErrorTestRoom_Smallest.rar?dl=0) [13MB ](https://www.dropbox.com/s/2t1suf4tmckhsse/ErrorTestRoom_Smallester.rar?dl=0) I won't repeat the description above, essentially same results even with less and less textures involved in the blend file. First 2 crash in the 80-90 frame range, smallest (13MB) crashes at around frame 130. No errors occur when there are no textures. **Exact steps for others to reproduce the error** Render the blend file above as an animation and it should start producing errors and crash at around frame 80-90. **Extra Notes** I've tried both OPTIX and CUDA and GPU only and GPU+CPU rendering and it produces the same error. CPU only rendering produces same error. Rendering the blend in 2.92 produces the same error. This does not happen when rendered in Eevee. If I start the render in the frames that it glitches out on it renders the frame without error. Rendering with "Persistent Data" option on fixes the issue but I'm not sure if it's a real fix.

Sienna Fuegonasus commented

2021-07-09 02:38:23 +02:00

Added subscriber: @Fuegonasus

Richard Antalik commented

2021-07-09 10:42:54 +02:00

Added subscriber: @iss

Richard Antalik commented

2021-07-09 10:42:54 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2021-07-09 10:42:54 +02:00

Thank you for report, but provided sample file is very big. Please simplify it as much as possible by removing objects not needed to reproduce the issue.

Sienna Fuegonasus commented

2021-07-09 10:53:16 +02:00

In #89747#1189017, @iss wrote:
Thank you for report, but provided sample file is very big. Please simplify it as much as possible by removing objects not needed to reproduce the issue.

It used to be a lot bigger because I thought reducing the number of objects and textures would fix the issue but it didn't. I will try to make it smaller and update the report.

> In #89747#1189017, @iss wrote: > Thank you for report, but provided sample file is very big. Please simplify it as much as possible by removing objects not needed to reproduce the issue. It used to be a lot bigger because I thought reducing the number of objects and textures would fix the issue but it didn't. I will try to make it smaller and update the report.

Sienna Fuegonasus commented

2021-07-09 12:42:29 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Richard Antalik commented

2021-07-09 13:34:05 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2021-07-09 13:34:05 +02:00

I am unable to reproduce this issue.

Please upload sample fle directly to this site. Does this issue happen when you render with CPU only? I can't check GPU rendering.

I am unable to reproduce this issue. Please upload sample fle directly to this site. Does this issue happen when you render with CPU only? I can't check GPU rendering.

Sienna Fuegonasus commented

2021-07-09 13:34:37 +02:00

Changed status from 'Needs User Info' to: 'Needs Triage'

Sienna Fuegonasus commented

2021-07-09 13:41:37 +02:00

Added a smaller size.

In #89747#1189182, @iss wrote:
I am unable to reproduce this issue.

Please upload sample fle directly to this site. Does this issue happen when you render with CPU only? I can't check GPU rendering.

Uploaded the smallest file to the site. Haven't tried CPU only, will try it the next time I can.

Added a smaller size. > In #89747#1189182, @iss wrote: > I am unable to reproduce this issue. > > Please upload sample fle directly to this site. Does this issue happen when you render with CPU only? I can't check GPU rendering. Uploaded the smallest file to the site. Haven't tried CPU only, will try it the next time I can.

Sienna Fuegonasus commented

2021-07-10 03:41:05 +02:00

In #89747#1189182, @iss wrote:
I am unable to reproduce this issue.

Please upload sample fle directly to this site. Does this issue happen when you render with CPU only? I can't check GPU rendering.

CPU only rendering produces the same error.

> In #89747#1189182, @iss wrote: > I am unable to reproduce this issue. > > Please upload sample fle directly to this site. Does this issue happen when you render with CPU only? I can't check GPU rendering. CPU only rendering produces the same error.

Philipp Oeser commented

2022-02-16 13:59:39 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2022-02-16 13:59:39 +01:00

Changed status from 'Needs Triage' to: 'Confirmed'

Philipp Oeser commented

2022-02-16 13:59:39 +01:00

Sorry this has slipped under the radar for so long.
I have given ErrorTestRoom_Smallester.rar (some textures are missing here, but I assume this is intentional?) a try in 3.2:

**System Information**
Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits
Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44
version: 3.2.0 Alpha, branch: master, commit date: 2022-02-15 21:20, hash: `rBd3b1cce4000b`

This rendered 243 frames, then indeed crashed (GPU memory and system memory consumption was pretty much stable throughout)

One thing I noticed was this in the console (on every frame):

Invalid graphics context in cuGraphicsUnregisterResource(cu_graphics_resource_) (intern/cycles/device/cuda/graphics_interop.cpp:36)

That message is the same as in #95651 (GPU error (Invalid graphics context in cuGraphicsUnregisterResource)), these might have the same underlying root cause, guess #render_cycles devs will need to check

Then on the last frames rendered I get this:

E0216 13:47:06.263782 225559 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory
E0216 13:47:06.264526 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
E0216 13:47:12.915915 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0240.png'
 Time: 00:07.95 (Saving: 00:00.02)

E0216 13:47:14.160032 225594 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory
E0216 13:47:14.160919 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
E0216 13:47:20.773739 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0241.png'
 Time: 00:07.85 (Saving: 00:00.01)

E0216 13:47:22.079187 225606 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory
E0216 13:47:22.081022 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
E0216 13:47:28.747159 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object.
Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0242.png'
 Time: 00:07.97 (Saving: 00:00.01)

Failed to create CUDA context (Operating system)

Refer to the Cycles GPU rendering documentation for possible solutions:
https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html

Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26)
Invalid context in cuStreamCreate(&cuda_stream_, CU_STREAM_NON_BLOCKING) (intern/cycles/device/cuda/queue.cpp:33)
Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31)
Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26)
Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31)
Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26)
Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31)
Invalid value in cuCtxDestroy_v2(cuContext) (intern/cycles/device/cuda/device_impl.cpp:138)
No device available to denoise on

Refer to the Cycles GPU rendering documentation for possible solutions:
https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html

Error: No device available to denoise on

Sorry this has slipped under the radar for so long. I have given `ErrorTestRoom_Smallester.rar` (some textures are missing here, but I assume this is intentional?) a try in 3.2: ``` **System Information** Operating system: Linux-5.13.0-0.rc6.45.fc35.x86_64-x86_64-with-glibc2.34.9000 64 Bits Graphics card: NVIDIA GeForce GTX 970M/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 495.44 version: 3.2.0 Alpha, branch: master, commit date: 2022-02-15 21:20, hash: `rBd3b1cce4000b` ``` This rendered 243 frames, then indeed crashed (GPU memory and system memory consumption was pretty much stable throughout) One thing I noticed was this in the console (on every frame): ``` Invalid graphics context in cuGraphicsUnregisterResource(cu_graphics_resource_) (intern/cycles/device/cuda/graphics_interop.cpp:36) ``` That message is the same as in #95651 (GPU error (Invalid graphics context in cuGraphicsUnregisterResource)), these might have the same underlying root cause, guess #render_cycles devs will need to check Then on the last frames rendered I get this: ``` E0216 13:47:06.263782 225559 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory E0216 13:47:06.264526 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. E0216 13:47:12.915915 225559 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0240.png' Time: 00:07.95 (Saving: 00:00.02) E0216 13:47:14.160032 225594 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory E0216 13:47:14.160919 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. E0216 13:47:20.773739 225594 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0241.png' Time: 00:07.85 (Saving: 00:00.01) E0216 13:47:22.079187 225606 graphics_interop.cpp:63] Error registering OpenGL buffer: Out of memory E0216 13:47:22.081022 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. E0216 13:47:28.747159 225606 display_driver.cpp:742] Error mapping BlenderDisplayDriver pixel buffer object. Saved: '/T89747/ErrorTestRoom_Smallester/ErrorTestRoom/render/0242.png' Time: 00:07.97 (Saving: 00:00.01) Failed to create CUDA context (Operating system) Refer to the Cycles GPU rendering documentation for possible solutions: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26) Invalid context in cuStreamCreate(&cuda_stream_, CU_STREAM_NON_BLOCKING) (intern/cycles/device/cuda/queue.cpp:33) Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31) Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26) Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31) Invalid value in cuCtxPushCurrent(device->cuContext) (intern/cycles/device/cuda/util.cpp:26) Invalid context in cuCtxPopCurrent(NULL) (intern/cycles/device/cuda/util.cpp:31) Invalid value in cuCtxDestroy_v2(cuContext) (intern/cycles/device/cuda/device_impl.cpp:138) No device available to denoise on Refer to the Cycles GPU rendering documentation for possible solutions: https://docs.blender.org/manual/en/latest/render/cycles/gpu_rendering.html Error: No device available to denoise on ```

Juan Gea commented

2022-02-16 17:37:37 +01:00

Added subscriber: @juang3d

Juan Gea commented

2022-02-16 17:37:37 +01:00

This seems to be the same error I reported here:

https://developer.blender.org/T95651

The example scene I have there is way smaller.

I suspect is related to the Nvidia driver version, with 510 on Linux and 511 on windows this happens, but I had no opportunity to test it with older drivers

P.S.: sorry you already mentioned it, I missed that, I’m on the phone

This seems to be the same error I reported here: https://developer.blender.org/T95651 The example scene I have there is way smaller. I suspect is related to the Nvidia driver version, with 510 on Linux and 511 on windows this happens, but I had no opportunity to test it with older drivers P.S.: sorry you already mentioned it, I missed that, I’m on the phone

Philipp Oeser commented

2022-02-18 10:35:57 +01:00

We now have #95837 (Regression: GPU memory accumulation in Cycles render) with the same error message. Not sure if this is exactly the same, but I've made that one High priority (since it also shows that memory is not freed on the GPU)
Strange thing in this report is that I think I watched GPU memory (and I think it was stable...)

We now have #95837 (Regression: GPU memory accumulation in Cycles render) with the same error message. Not sure if this is exactly the same, but I've made that one High priority (since it also shows that memory is not freed on the GPU) Strange thing in this report is that I think I watched GPU memory (and I think it was stable...)

blender-admin commented

2022-02-18 14:31:39 +01:00

This issue was referenced by e4b7d52fe4

This issue was referenced by e4b7d52fe4fe3076f5f68ff575c200f5cf16e416

Sergey Sharybin commented

2022-02-18 15:32:33 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Sergey Sharybin closed this issue

2022-02-18 15:32:33 +01:00

Sergey Sharybin self-assigned this 2022-02-18 15:32:33 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycles Render - Textures Disappear then Crashes the Render #89747