Regression: Memory leak during rendering #105148

New Issue

Kent Davis · 2023-02-23T18:36:03+01:00

Kent Davis commented

2023-02-23 18:36:03 +01:00

System Information
Operating system: macOS-13.3-x86_64-i386-64bit 64 Bits
Graphics card: Metal API AMD Radeon Pro 575 1.2

Blender Version
Caused by 02c2970983

Short description of error
Command + 12 Render is fail.

You can use my file "Horizontal Video 1.0.2.blend"
Command + F12 start at 8:51 PM and continue few hours until become black screen itself at about 8 AM and render complete cause CRASH at 8:19 AM!
Uncheck Tiling checkbox: image

Hardware Overview:

Model Name: iMac
Model Identifier: iMac18,3
Processor Name: Quad-Core Intel Core i5
Processor Speed: 3.5 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 6 MB
Memory: 16 GB
System Firmware Version: 499.40.2.0.0
OS Loader Version: 577~109
SMC Version (system): 2.41f2
Serial Number (system): D25WC0D6J1GP
Hardware UUID: E2E4C74A-7218-56CD-8FEA-7FBD6409C225
Provisioning UDID: E2E4C74A-7218-56CD-8FEA-7FBD6409C225

===================================

Radeon Pro 575:

Chipset Model: Radeon Pro 575
Type: GPU
Bus: PCIe
PCIe Lane Width: x16
VRAM (Total): 4 GB
Vendor: AMD (0x1002)
Device ID: 0x67df
Revision ID: 0x00c4
ROM Revision: 113-D000AA-931
VBIOS Version: 113-D0001A1P-025
EFI Driver Version: 01.00.931
Metal Support: Metal 2
Displays:
iMac:
Display Type: Built-In Retina LCD
Resolution: Retina 5K (5120 x 2880)
Framebuffer Depth: 30-Bit Color (ARGB2101010)
Main Display: Yes
Mirror: Off
Online: Yes
Automatically Adjust Brightness: No
Connection Type: Internal

Exact steps for others to reproduce the error

Open file and Render animation. Use Metal backend.

Crashes after ~120 frames, but it goes very quickly.
With openGL it does not crash. It says, that system is out of GPU memory (looks like with Metal it tries to make same error message, but does not have chance).

**System Information** Operating system: macOS-13.3-x86_64-i386-64bit 64 Bits Graphics card: Metal API AMD Radeon Pro 575 1.2 **Blender Version** Caused by 02c2970983215b67feedd0b2aa4b40aed269b707 **Short description of error** Command + 12 Render is fail. - You can use my file "Horizontal Video 1.0.2.blend" - Command + F12 start at 8:51 PM and continue few hours until become black screen itself at about 8 AM and render complete cause CRASH at 8:19 AM! - Uncheck Tiling checkbox: [image](/attachments/7ed20f9b-0b75-43f5-ac82-3f6d27462f2c) ![Preferences > system](/attachments/4086c15f-76ea-484b-ad81-d057c716cc97) ![image](/attachments/bdf45cf9-4df1-4b44-a053-191f0fcdcf63) ![image](/attachments/8aa71ba0-cd86-4f69-b0f2-a1a84c635dee) Hardware Overview: Model Name: iMac Model Identifier: iMac18,3 Processor Name: Quad-Core Intel Core i5 Processor Speed: 3.5 GHz Number of Processors: 1 Total Number of Cores: 4 L2 Cache (per Core): 256 KB L3 Cache: 6 MB Memory: 16 GB System Firmware Version: 499.40.2.0.0 OS Loader Version: 577~109 SMC Version (system): 2.41f2 Serial Number (system): D25WC0D6J1GP Hardware UUID: E2E4C74A-7218-56CD-8FEA-7FBD6409C225 Provisioning UDID: E2E4C74A-7218-56CD-8FEA-7FBD6409C225 =================================== Radeon Pro 575: Chipset Model: Radeon Pro 575 Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 4 GB Vendor: AMD (0x1002) Device ID: 0x67df Revision ID: 0x00c4 ROM Revision: 113-D000AA-931 VBIOS Version: 113-D0001A1P-025 EFI Driver Version: 01.00.931 Metal Support: Metal 2 Displays: iMac: Display Type: Built-In Retina LCD Resolution: Retina 5K (5120 x 2880) Framebuffer Depth: 30-Bit Color (ARGB2101010) Main Display: Yes Mirror: Off Online: Yes Automatically Adjust Brightness: No Connection Type: Internal **Exact steps for others to reproduce the error** Open [file](https://projects.blender.org/attachments/29d3bae2-ecd3-4200-af06-7d1a13eb66b8) and Render animation. Use Metal backend. Crashes after ~120 frames, but it goes very quickly. With openGL it does not crash. It says, that system is out of GPU memory (looks like with Metal it tries to make same error message, but does not have chance).

image.png

601 KiB

Blender-2023-02-23-090538.ips

53 KiB

image.png

1.4 MiB

Horizontal Video 3.4.1.zip

32 MiB

image.png

622 KiB

image.png

432 KiB

image.png

588 KiB

image.png

392 KiB

Kent Davis added the

labels 2023-02-23 18:36:04 +01:00

Germano Cavalcante commented

2023-02-24 14:47:22 +01:00

Thanks for the report and the images, but despite so much information, it's still not clear what the problem is.

Less information is sometimes better as long as it makes the problem clear.

Thanks for the report and the images, but despite so much information, it's still not clear what the problem is. Less information is sometimes better as long as it makes the problem clear.

Germano Cavalcante added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-02-24 14:47:41 +01:00

Kent Davis commented

2023-02-26 17:19:11 +01:00

@mano-wii

Oh well I show you my youtube you can see.
Render go up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up and up cause crash or out of memory of ram plus Videocard GPU ram become black screen.
Flame fire never go up, up, up, up, up, up NEVER. There up then "clean my mac" ram and GPU video go down memory then go up memory then go down memory is best.
Copy from Flame Fire memory code and paste to RENDER code for memory like RENDER memory go up then go down then go up then go down clean my mac memory itself.

Youtube you can see there make crash too much since from Blender 2.8 until now 3.6.0
https://youtu.be/tWyu0MSVsXk

@PratikPB2123 You may put Mac notification.

@mano-wii Oh well I show you my youtube you can see. Render go up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up, up and up cause crash or out of memory of ram plus Videocard GPU ram become black screen. Flame fire never go up, up, up, up, up, up NEVER. There up then "clean my mac" ram and GPU video go down memory then go up memory then go down memory is best. Copy from Flame Fire memory code and paste to RENDER code for memory like RENDER memory go up then go down then go up then go down clean my mac memory itself. Youtube you can see there make crash too much since from Blender 2.8 until now 3.6.0 https://youtu.be/tWyu0MSVsXk @PratikPB2123 You may put Mac notification.

3.5.0 Fire 1.0.2 February 25, 2023.zip

583 KiB

Iliya Katushenock commented

2023-02-26 17:39:45 +01:00

Hello. Try to attach the file an example (in which problems arise), and also, I see at the end of the video that you have a message with the tracing of the stack at the end.
Is it possible to attach a file with the text of this error message?

Hello. Try to attach the file an example (in which problems arise), and also, I see at the end of the video that you have a message with the tracing of the stack at the end. Is it possible to attach a file with the text of this error message?

Kent Davis commented

2023-02-26 18:46:31 +01:00

@mod_moder
Yes I forget to put .ips file.
I am full deaf and I am not good english myself. I do know sign language as well.

@mod_moder Yes I forget to put .ips file. I am full deaf and I am not good english myself. I do know sign language as well.

Blender-2023-02-26-071638.ips

49 KiB

👍 1

Kent Davis commented

2023-02-26 22:22:53 +01:00

There render crash too much. See other .ips

Blender-2023-02-26-132020.ips

56 KiB

Germano Cavalcante commented

2023-02-27 17:56:55 +01:00

Apparently the crash happens in blender::gpu::MTLTexture::update_sub(int, int*, int*, eGPUDataFormat, void const*)

{"imageOffset":2537,"symbol":"_platform_memmove$VARIANT$Haswell","symbolLocation":41,"imageIndex":78},
{"imageOffset":129932974,"symbol":"blender::gpu::MTLTexture::update_sub(int, int*, int*, eGPUDataFormat, void const*)","symbolLocation":1534,"imageIndex":0},
{"imageOffset":129587739,"symbol":"GPU_texture_update","symbolLocation":123,"imageIndex":0},
{"imageOffset":11551048,"symbol":"blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>::do_full_update_gpu_texture(blender::draw::image_engine::TextureInfo&, blender::draw::image_engine::IMAGE_InstanceData&, ImageUser const*) const","symbolLocation":376,"imageIndex":0},
{"imageOffset":11544911,"symbol":"blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>::update_textures(blender::draw::image_engine::IMAGE_InstanceData&, Image*, ImageUser*) const","symbolLocation":399,"imageIndex":0},
{"imageOffset":11542316,"symbol":"blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>::image_sync(blender::draw::image_engine::IMAGE_Data*, Image*, ImageUser*) const","symbolLocation":300,"imageIndex":0},
{"imageOffset":11540862,"symbol":"blender::draw::image_engine::ImageEngine<blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>>::image_sync()","symbolLocation":462,"imageIndex":0},
{"imageOffset":11539289,"symbol":"blender::draw::image_engine::IMAGE_cache_init(void*)","symbolLocation":345,"imageIndex":0},
{"imageOffset":11403563,"symbol":"drw_engines_cache_init","symbolLocation":155,"imageIndex":0},{"imageOffset":11400614,"symbol":"DRW_draw_render_loop_2d_ex","symbolLocation":630,"imageIndex":0},
{"imageOffset":25812185,"symbol":"image_main_region_draw","symbolLocation":681,"imageIndex":0},
{"imageOffset":15529041,"symbol":"ED_region_do_draw","symbolLocation":337,"imageIndex":0},
{"imageOffset":9694285,"symbol":"wm_draw_update","symbolLocation":1805,"imageIndex":0},
{"imageOffset":9679872,"symbol":"WM_main","symbolLocation":48,"imageIndex":0},
{"imageOffset":1669640,"symbol":"main","symbolLocation":888,"imageIndex":0},
{"imageOffset":25631,"symbol":"start","symbolLocation":1903,"imageIndex":79}]},

Informations that would also be useful in the report:

Better steps to reproduce the problem
the name of the .blend file used to render.
Does it work with OpenGL instead of Metal?

Recommendations about the video on YouTube:

12 minutes is a long time. The recommended is a few seconds.
Attach the video in the report instead of Youtube
The configurations in the .blend file does not need to be pointed out, (they can be consulted by the developer in the file itself).

I'm not sure yet how to reproduce the problem.

Apparently the crash happens in `blender::gpu::MTLTexture::update_sub(int, int*, int*, eGPUDataFormat, void const*)` ``` {"imageOffset":2537,"symbol":"_platform_memmove$VARIANT$Haswell","symbolLocation":41,"imageIndex":78}, {"imageOffset":129932974,"symbol":"blender::gpu::MTLTexture::update_sub(int, int*, int*, eGPUDataFormat, void const*)","symbolLocation":1534,"imageIndex":0}, {"imageOffset":129587739,"symbol":"GPU_texture_update","symbolLocation":123,"imageIndex":0}, {"imageOffset":11551048,"symbol":"blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>::do_full_update_gpu_texture(blender::draw::image_engine::TextureInfo&, blender::draw::image_engine::IMAGE_InstanceData&, ImageUser const*) const","symbolLocation":376,"imageIndex":0}, {"imageOffset":11544911,"symbol":"blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>::update_textures(blender::draw::image_engine::IMAGE_InstanceData&, Image*, ImageUser*) const","symbolLocation":399,"imageIndex":0}, {"imageOffset":11542316,"symbol":"blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>::image_sync(blender::draw::image_engine::IMAGE_Data*, Image*, ImageUser*) const","symbolLocation":300,"imageIndex":0}, {"imageOffset":11540862,"symbol":"blender::draw::image_engine::ImageEngine<blender::draw::image_engine::ScreenSpaceDrawingMode<blender::draw::image_engine::ScreenTileTextures<1ul>>>::image_sync()","symbolLocation":462,"imageIndex":0}, {"imageOffset":11539289,"symbol":"blender::draw::image_engine::IMAGE_cache_init(void*)","symbolLocation":345,"imageIndex":0}, {"imageOffset":11403563,"symbol":"drw_engines_cache_init","symbolLocation":155,"imageIndex":0},{"imageOffset":11400614,"symbol":"DRW_draw_render_loop_2d_ex","symbolLocation":630,"imageIndex":0}, {"imageOffset":25812185,"symbol":"image_main_region_draw","symbolLocation":681,"imageIndex":0}, {"imageOffset":15529041,"symbol":"ED_region_do_draw","symbolLocation":337,"imageIndex":0}, {"imageOffset":9694285,"symbol":"wm_draw_update","symbolLocation":1805,"imageIndex":0}, {"imageOffset":9679872,"symbol":"WM_main","symbolLocation":48,"imageIndex":0}, {"imageOffset":1669640,"symbol":"main","symbolLocation":888,"imageIndex":0}, {"imageOffset":25631,"symbol":"start","symbolLocation":1903,"imageIndex":79}]}, ``` **Informations that would also be useful in the report:** - Better steps to reproduce the problem - the name of the .blend file used to render. - Does it work with `OpenGL` instead of `Metal`? **Recommendations about the video on YouTube:** - 12 minutes is a long time. The recommended is a few seconds. - Attach the video in the report instead of Youtube - The configurations in the .blend file does not need to be pointed out, (they can be consulted by the developer in the file itself). I'm not sure yet how to reproduce the problem.

Germano Cavalcante added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Regression: Memory leak during rendering #105148