Cycles experiences freezes when there are disconnected packed textures #117888

New Issue

LTZ · 2024-02-06T11:23:27+01:00

LTZ commented

2024-02-06 11:23:27 +01:00

System Information
Operating system:win 10
Graphics card:rtx3060/3080

Blender Version
4.0.2

Short description of error

Use the Cycles renderer.
Use 16k resolution textures (the specific boundaries have not been tested, but it seems there is a minor impact at 8k resolution).
Pack textures into the ". blend" file.

Under these conditions, adjusting parameters on the Principled Shader when textures are connected will not cause rendering lag. If disconnected and the texture is not deleted, severe rendering lag will occur.

I attempted to reduce the size of the textures and found that a 20MB texture at 16k resolution still causes lag, although it appears to be less severe. The correlation with texture format has not been tested.

This looks strange indeed. I recall that if textures are not connected to the shader, they shouldn't be involved in calculations. Now it seems to be the opposite.

It seems that there are other variables that might affect the occurrence of this situation, but I haven't summarized them yet.

Sorry, I can't provide the file. The high-resolution image is too large for me to upload. However, it should be easy to reproduce

（Translate by software）

**System Information** Operating system:win 10 Graphics card:rtx3060/3080 **Blender Version** 4.0.2 **Short description of error** 1. Use the Cycles renderer. 2. Use 16k resolution textures (the specific boundaries have not been tested, but it seems there is a minor impact at 8k resolution). 3. Pack textures into the ". blend" file. Under these conditions, adjusting parameters on the Principled Shader when textures are connected will not cause rendering lag. If disconnected and the texture is not deleted, severe rendering lag will occur. I attempted to reduce the size of the textures and found that a 20MB texture at 16k resolution still causes lag, although it appears to be less severe. The correlation with texture format has not been tested. This looks strange indeed. I recall that if textures are not connected to the shader, they shouldn't be involved in calculations. Now it seems to be the opposite. It seems that there are other variables that might affect the occurrence of this situation, but I haven't summarized them yet. Sorry, I can't provide the file. The high-resolution image is too large for me to upload. However, it should be easy to reproduce （Translate by software）

This runs smoothly.png

734 KiB

However, it lags at this point.png

470 KiB

LTZ added the

labels 2024-02-06 11:23:28 +01:00

Iliya Katushenock commented

2024-02-07 01:01:05 +01:00

Have no any issue with 3 8x8k texture in cycles in latest 4.1:

Have no any issue with 3 8x8k texture in cycles in latest 4.1: ![image](/attachments/ca47d6fa-f0f5-4433-ad15-9f06dbaa3851)

image.png

733 KiB

Pratik Borhade commented

2024-02-07 06:37:28 +01:00

Hi, thanks for the report. Could attach system info: Help > Save system info
Also would be good to know whether this was observed during CPU or GPU render.
Have you checked CPU/GPU/memory usage during the lag?

Hi, thanks for the report. Could attach system info: `Help > Save system info` Also would be good to know whether this was observed during CPU or GPU render. Have you checked CPU/GPU/memory usage during the lag?

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-02-07 06:37:42 +01:00

LTZ commented

2024-02-07 08:02:18 +01:00

@mod_moder I use four 16k*16k texture maps, and I pack them together and disconnect them from the shader. At this point, adjusting the shader parameters causes the software to crash. I don't think it's a hardware issue because if I connect the texture maps to the shader, the software doesn't crash.
There may be translation inaccuracies. I'm not sure if the meaning has been clearly conveyed. I will upload a screen recording

@mod_moder I use four 16k*16k texture maps, and I pack them together and disconnect them from the shader. At this point, adjusting the shader parameters causes the software to crash. I don't think it's a hardware issue because if I connect the texture maps to the shader, the software doesn't crash. There may be translation inaccuracies. I'm not sure if the meaning has been clearly conveyed. I will upload a screen recording

bba9223ad00b8fbe0995074f5b85e17e.mp4

5.1 MiB

LTZ commented

2024-02-07 08:14:33 +01:00

@PratikPB2123
I conducted experiments using two PCs.
Both systems are running Windows 10, and the Blender versions are mostly the same (there may be slight differences in plugins, but I don't think the issue lies there).
PC1:

GPU: Nvidia GeForce RTX 3060 12GB
CPU: AMD Ryzen 9 7900X
RAM: 64GB
PC2:
GPU: Nvidia GeForce RTX 3080 10GB
CPU: AMD Ryzen 9 3950X
RAM: 64GB
I will upload a file from PC1, but I don't think the issue lies there because there aren't any severe crashes when the texture is connected to the shader, as seen in the video I uploaded earlier.

When the crash occurs, I am in GPU preview mode with the Cycles renderer.

@PratikPB2123 I conducted experiments using two PCs. Both systems are running Windows 10, and the Blender versions are mostly the same (there may be slight differences in plugins, but I don't think the issue lies there). PC1: GPU: Nvidia GeForce RTX 3060 12GB CPU: AMD Ryzen 9 7900X RAM: 64GB PC2: GPU: Nvidia GeForce RTX 3080 10GB CPU: AMD Ryzen 9 3950X RAM: 64GB I will upload a file from PC1, but I don't think the issue lies there because there aren't any severe crashes when the texture is connected to the shader, as seen in the video I uploaded earlier. When the crash occurs, I am in GPU preview mode with the Cycles renderer.

system-info.txt

24 KiB

Pratik Borhade commented

2024-02-14 06:50:26 +01:00

Thanks. Unable to confirm though in 4.2 build.
Does this happen after disconnecting image-textures from mapping node?
Could you share blend file?
And also check with factory settings: File > Defaults > Load Factory Settings

Thanks. Unable to confirm though in 4.2 build. Does this happen after disconnecting image-textures from mapping node? Could you share blend file? And also check with factory settings: `File > Defaults > Load Factory Settings`

LTZ commented

2024-02-24 06:15:32 +01:00

@PratikPB2123 I have switched to a new computer with an RTX 4080 and an i7-13700K processor, running Windows 11. I have also reset Blender, but the previous issues still persist. I have recorded a complete video for reference. All textures used in the video have a resolution of 8k and are over 100MB in size.
The phenomenon remains the same: when I pack the textures without linking them to the shader, there is lag in the operation.

@PratikPB2123 I have switched to a new computer with an RTX 4080 and an i7-13700K processor, running Windows 11. I have also reset Blender, but the previous issues still persist. I have recorded a complete video for reference. All textures used in the video have a resolution of 8k and are over 100MB in size. The phenomenon remains the same: when I pack the textures without linking them to the shader, there is lag in the operation.

1708750920829.mp4

112 MiB

Pratik Borhade commented

2024-03-01 09:54:41 +01:00

Video is not visible unfortunately :/

BTW @Alaska can you replicate this?

Video is not visible unfortunately :/ BTW @Alaska can you replicate this?

LTZ commented

2024-03-01 10:38:08 +01:00

@PratikPB2123
You can try downloading the video,
ps:
Correct the previous response
Texture size is 16k*16k

@PratikPB2123 You can try downloading the video, ps: Correct the previous response Texture size is 16k*16k

Alaska commented

2024-03-01 11:48:16 +01:00

I can reproduce this issue on the CPU (Ryzen 9 5950X and M1 Pro), and GPU (RTX 4090) in Cycles on Windows and macOS with Blender 4.0.2 and 4.2. There was no issue with EEVEE in my testing. So I will add this to the Cycles module.

I quickly profiled it, and it seems Cycles gets stuck in the image manager when this hang occurs, and RAM usuage typically sees a massive increase during this. So my guess is Cycles incorrectly tries loading the texture when it's not needed in this configuration.

I can reproduce this issue on the CPU (Ryzen 9 5950X and M1 Pro), and GPU (RTX 4090) in Cycles on Windows and macOS with Blender 4.0.2 and 4.2. There was no issue with EEVEE in my testing. So I will add this to the Cycles module. I quickly profiled it, and it seems Cycles gets stuck in the image manager when this hang occurs, and RAM usuage typically sees a massive increase during this. So my guess is Cycles incorrectly tries loading the texture when it's not needed in this configuration.

Alaska added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycles experiences freezes when there are disconnected packed textures #117888