Maniphest T96471

Apple Metal on intel macOS-12.3 & AMD Radeon Pro 5700 XT iMac crashing/hanging and immense memory usage.
Closed, ArchivedBUG
Actions

Assigned To
None
Authored By
Guido (Nurb2Kea)
Mar 15 2022, 12:08 AM
Tags
  • BF Blender
  • Platform: macOS
Subscribers
Germano Cavalcante (mano-wii)
Guido (Nurb2Kea)
Pratik Borhade (PratikPB2123)

Description

System Information
Operating system: macOS-12.3-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13

Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: rBc77597cd0e15
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-03-14 19:06, hash: rBfc259d4c30cb

Short description of error
Switching from solid to rendered viewport OR start rendering ends in hanging blender app.
Same for switching between GPU Supported and Experimental when in solit view.

Just using CPU works normal, but as soon as you switch to GPU or start a render ...

Exact steps for others to reproduce the error
USE : Latest macos 12.3 intel, AMD Radeon Pro 5700 XT, xcode 13.2.
I used here the downloaded blender 3.1.0 and compiled blender 3.2.0 version.

It was tested on factory settings!

EDIT: After leaving the room for a ciggy with hanging blender, it started rendering. Meaning to render Suzanne with a light takes at least several minutes to calculate, then the render starts and ends in a few seconds. Every time you want to render or restart blender.
MEANS: The long calculating (for initialising the graphics card ) takes place every time I start blender PLUS the long calculating time for the scene.

Viewport is the same. Works with the GPU but very slow. Rendering with CPU&GPU doubles the render time.
(Persistant data is switched off but was also tested ON with the same result.)
All in all, every time it calculates the scene first via CPU for a long time, then it renders, what brings the overall rendertime to the same result as rendering only with a CPU on this basic intel iMac setup!!
Also the overall performace of the OS is super laggy / unusable. Means opening a text editor for example, thakes several seconds...

16-March-2022_02.49_02.blend3 MBDownload

This file on CPU only rendering:

Reduced RAM from 64 GB to 4.2 GB RAM
Calculation time: 1 min 11 sec
Altogether Render time: 6 min 43 sec

This file on GPU only rendering:

Reduced RAM from 64 GB to 6.7 GB RAM
Calculation time: 18 min 32 sec
Altogether Render time: --- stopped the render after 22 min. AND no Sample was rendered at all !

simple scene:

This shows the CPU and GPU usage when trying to render with GPU only. Calculating only done on CPU.
IF rendering only with CPU the calculating time on the CPU is not that long as you can see above.

the CPU render:

Related Objects

Event Timeline

Guido (Nurb2Kea) created this task.Mar 15 2022, 12:08 AM
Guido (Nurb2Kea) updated the task description.Mar 15 2022, 12:50 AM
Guido (Nurb2Kea) updated the task description.Mar 16 2022, 3:13 AM
Guido (Nurb2Kea) renamed this task from macOS-12.3 & AMD Radeon Pro 5700 XT crashing/hanging to Apple Metal on intel macOS-12.3 & AMD Radeon Pro 5700 XT iMac crashing/hanging and immense memory usage..Mar 16 2022, 4:05 AM
Guido (Nurb2Kea) updated the task description.
Pratik Borhade (PratikPB2123) changed the task status from Needs Triage to Needs Information from User.Mar 16 2022, 7:39 AM
Pratik Borhade (PratikPB2123) added a subscriber: Pratik Borhade (PratikPB2123).

Hi, thanks for the report.

Issue is probably same as described in- T96252

Can you check again with latest macOS update

Do you have this issue on previous blender versions? (say 3.0.0, 2,.93LTS)

Does this happen with viewport render or final render?

Guido (Nurb2Kea) added a comment.Mar 16 2022, 10:46 AM

I use the latest macOS 12.3 already, as of the day of this report when the 12.3 update arrived !
Those versions (say 3.0.0, 2,.93LTS) AREN'T able to, because Metal for Intel Mac's and AMD cards was introduced with blender 3.1, 3.2 etc...

Does this happen with viewport render or final render? Yepp, SEE ABOVE !

All answered already in the report, see above. And slidly different than T96252.

THX

Pratik Borhade (PratikPB2123) changed the task status from Needs Information from User to Needs Triage.Mar 16 2022, 10:52 AM
Pratik Borhade (PratikPB2123) added a project: Platform: macOS.
Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Needs Information from User.Mar 17 2022, 10:11 PM
Germano Cavalcante (mano-wii) added a subscriber: Germano Cavalcante (mano-wii).

This doesn't seem like a Mac-only issue and I'm not sure if it's a GPU issue.
Here with an AMD with CPU rendering only I experience a crash.

The problem seems to be the fact that the Mesh light object uses Adaptive Subdivision which causes, in the layout used, a very high usage of CPU and memory resources.
While we want to improve Blender to handle such cases memory gracefully, this is not currently considered a bug.

@Guido (Nurb2Kea), could you check if the problem is really with the Adaptive Subdivision?

Guido (Nurb2Kea) added a comment.Mar 17 2022, 10:37 PM

Well Germano Cavalcante, do you except a hug ! :-)

You're right, Adaptive Subdivision and the fact that the meshlight also has a shape key on it, caused the problem. I just switched it off!
Rendering is down to 1min 29sec and only uses 4736.45M.

Haven't heard and had the problem yet, that Adaptive Subdivision and rendering has such a long calculation time on a simple Adaptive Subdivision + shape key.
Most of the times I leave those Adaptive Subdivisions unapplied for later changing and test renders.
(Also wondering how to render those details with Adaptive Subdivision turned OFF ???)

Anyways, solved for me but that should be communicated with all the dev's for a fix.

Germano Cavalcante (mano-wii) closed this task as Archived.Mar 18 2022, 12:56 PM

Good to know that we identified the problem.

In T96471#1324970, @Guido (Nurb2Kea) wrote:

(...)
Anyways, solved for me but that should be communicated with all the dev's for a fix.

A valid report needs to be simple and straightforward about the bug. But the scenario described in this one is not clear and it took a lot of time for me to identify the problem.
(We require the bug reporter to narrow down the problem).

It's also still unclear if it's actually a bug in Adaptive Subdivision + shape key or a limitation in the scenario.

If you think you found a bug, please submit a new report and carefully follow the instructions. Be sure to provide a .blend file simplified and the exact steps to reproduce the problem.

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

It's also good to keep in mind that Adaptive Subdivision hasn't been maintained for a long time, which is one of the reasons it's still experimental.

Guido (Nurb2Kea) mentioned this in T96370: Blender stopped rendering.Mar 24 2022, 2:47 PM
Pratik Borhade (PratikPB2123) mentioned this in T96880: Regression: 'Viewport Render Animation' stuck and crashes.Mar 31 2022, 6:42 AM
Guido (Nurb2Kea) added a comment.Apr 1 2022, 3:25 PM

Still continuing on latest blender version:

System Information
Operating system: macOS-12.3-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5700 XT OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.8.13

Blender Version
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-03-31 17:14, hash: rB42853bacc973

Guido (Nurb2Kea) changed the subtype of this task from "Report" to "Bug".Apr 1 2022, 3:28 PM