Blender 3.1a sticks and doesn't render when rendering with Metal GPU on Mac #94858

New Issue

cotooleimages@gmail.com · 2022-01-12T21:19:22+01:00

2022-01-12 21:19:22 +01:00

System Information
Operating system: macOS-12.1-arm64-arm-64bit 64 Bits
Graphics card: Apple M1 Max Apple 4.1 Metal - 76.3

Blender Version
Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-10 22:45, hash: 922ae55a16
Worked: This project rendered on the same 3.1a build on the CPU, just not on the GPU.

Short description of error
When I render this scene on the GPU, blender just sticks and doesn't render. (Blender 3.1a has always rendered other scenes perfectly on the GPU.)

Exact steps for others to reproduce the error

Open .blend file
Render as Image (F12)
The issue may be at the fault of either the fact that I have displacement on the plane, or that I have 2 render layers
try1.blend

**System Information** Operating system: macOS-12.1-arm64-arm-64bit 64 Bits Graphics card: Apple M1 Max Apple 4.1 Metal - 76.3 **Blender Version** Broken: version: 3.1.0 Alpha, branch: master, commit date: 2022-01-10 22:45, hash: `922ae55a16` Worked: This project rendered on the same 3.1a build on the CPU, just not on the GPU. **Short description of error** When I render this scene on the GPU, blender just sticks and doesn't render. (Blender 3.1a has always rendered other scenes perfectly on the GPU.) **Exact steps for others to reproduce the error** - Open .blend file - Render as Image (`F12`) The issue may be at the fault of either the fact that I have displacement on the plane, or that I have 2 render layers [try1.blend](https://archive.blender.org/developer/F12802645/try1.blend)

cotooleimages@gmail.com commented

2022-01-12 21:19:22 +01:00

Added subscriber: @BlenderChris

Richard Antalik commented

2022-01-18 19:48:21 +01:00

Added subscriber: @iss

Richard Antalik commented

2022-01-18 19:48:21 +01:00

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

Richard Antalik commented

2022-01-18 19:48:21 +01:00

Not sure if I understand this report - do you mean, that when you render the image, nothing will happen? Checking here this causes crash, but I waned to clarify before I confirm.

cotooleimages@gmail.com commented

2022-01-18 19:52:17 +01:00

In #94858#1290454, @iss wrote:
Not sure if I understand this report - do you mean, that when you render the image, nothing will happen? Checking here this causes crash, but I waned to clarify before I confirm.

Yes. That's what I'm meaning. Just simply render the image.

> In #94858#1290454, @iss wrote: > Not sure if I understand this report - do you mean, that when you render the image, nothing will happen? Checking here this causes crash, but I waned to clarify before I confirm. Yes. That's what I'm meaning. Just simply render the image.

Pratik Borhade commented

2022-01-19 04:55:20 +01:00

Added subscriber: @PratikPB2123

Pratik Borhade commented

2022-01-19 04:55:20 +01:00

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

Pratik Borhade commented

2022-01-19 04:55:20 +01:00

Thanks for the report. I get the crash when rendering your scene
Even appear before the the Cycles-X merge. Need to find when exactly it came.

This project rendered on the same 3.1a build on the CPU,

I can reproduce on CPU.

blender.exe         :0x00007FF621CFF700  image_acquire_ibuf
blender.exe         :0x00007FF621CF8150  BKE_image_acquire_ibuf
blender.exe         :0x00007FF6222AC990  Image_size_get
blender.exe         :0x00007FF622DF48F0  ccl::BlenderImageLoader::load_metadata
blender.exe         :0x00007FF623129680  ccl::ImageManager::load_image_metadata
blender.exe         :0x00007FF623128A00  ccl::ImageManager::device_load_image
blender.exe         :0x00007FF623127850  std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl ccl::ImageManager::*)(ccl::Devic
blender.exe         :0x00007FF62613B340  tbb::internal::function_task<std::function<void __cdecl(void)> >::execute
tbb.dll             :0x00007FFBAF48F690  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFBAF48F690  tbb::recursive_mutex::scoped_lock::internal_try_acquire
tbb.dll             :0x00007FFBAF4851B0  tbb::interface7::internal::isolate_within_arena
tbb.dll             :0x00007FFBAF48A470  tbb::task_scheduler_init::terminate
tbb.dll             :0x00007FFBAF48DBD0  tbb::thread_bound_filter::try_process_item
tbb.dll             :0x00007FFBAF48DBD0  tbb::thread_bound_filter::try_process_item
ucrtbase.dll        :0x00007FFBC3051B20  configthreadlocale
KERNEL32.DLL        :0x00007FFBC3927020  BaseThreadInitThunk
ntdll.dll           :0x00007FFBC5842630  RtlUserThreadStart```

Thanks for the report. I get the crash when rendering your scene Even appear before the the Cycles-X merge. Need to find when exactly it came. > This project rendered on the same 3.1a build on the CPU, I can reproduce on CPU. ```lines=10 blender.exe :0x00007FF621CFF700 image_acquire_ibuf blender.exe :0x00007FF621CF8150 BKE_image_acquire_ibuf blender.exe :0x00007FF6222AC990 Image_size_get blender.exe :0x00007FF622DF48F0 ccl::BlenderImageLoader::load_metadata blender.exe :0x00007FF623129680 ccl::ImageManager::load_image_metadata blender.exe :0x00007FF623128A00 ccl::ImageManager::device_load_image blender.exe :0x00007FF623127850 std::_Func_impl_no_alloc<std::_Binder<std::_Unforced,void (__cdecl ccl::ImageManager::*)(ccl::Devic blender.exe :0x00007FF62613B340 tbb::internal::function_task<std::function<void __cdecl(void)> >::execute tbb.dll :0x00007FFBAF48F690 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFBAF48F690 tbb::recursive_mutex::scoped_lock::internal_try_acquire tbb.dll :0x00007FFBAF4851B0 tbb::interface7::internal::isolate_within_arena tbb.dll :0x00007FFBAF48A470 tbb::task_scheduler_init::terminate tbb.dll :0x00007FFBAF48DBD0 tbb::thread_bound_filter::try_process_item tbb.dll :0x00007FFBAF48DBD0 tbb::thread_bound_filter::try_process_item ucrtbase.dll :0x00007FFBC3051B20 configthreadlocale KERNEL32.DLL :0x00007FFBC3927020 BaseThreadInitThunk ntdll.dll :0x00007FFBC5842630 RtlUserThreadStart```

Germano Cavalcante commented

2022-01-20 16:23:58 +01:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2022-01-20 16:23:58 +01:00

In fact there is a problem with tiled images causing a crash that prevents testing the original reported bug.
It is important to know what causes the crash and to report it separately.
I'll keep the file to investigate further.

In fact there is a problem with tiled images causing a crash that prevents testing the original reported bug. It is important to know what causes the crash and to report it separately. I'll keep the file to investigate further.

cotooleimages@gmail.com commented

2022-01-20 17:20:47 +01:00

Thank you very much! I was so stoked when Metal came in but kinda disappointed when I ran into this bug.

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender 3.1a sticks and doesn't render when rendering with Metal GPU on Mac #94858