Apple Metal on intel macOS-12.3 & AMD Radeon Pro 5700 XT iMac crashing/hanging and immense memory usage. #96471

Closed
opened 11 months ago by Nurb2Kea · 13 comments

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: c77597cd0e
Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-03-14 19:06, hash: fc259d4c30

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!
Screen Shot 2022-03-15 at 12.02.24 am.jpg

Screen Shot 2022-03-14 at 11.54.42 pm.jpg

Screen Shot 2022-03-14 at 11.54.05 pm.jpg

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.blend

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:
Screen Shot-01.jpg

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.
Screen Shot 2022-03-16 at 3.23.50 am.jpg

the CPU render:
Screen Shot 2022-03-16 at 3.45.53 am.jpg

**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: `c77597cd0e` Broken: version: 3.2.0 Alpha, branch: master, commit date: 2022-03-14 19:06, hash: `fc259d4c30` **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! ![Screen Shot 2022-03-15 at 12.02.24 am.jpg](https://archive.blender.org/developer/F12928072/Screen_Shot_2022-03-15_at_12.02.24_am.jpg) ![Screen Shot 2022-03-14 at 11.54.42 pm.jpg](https://archive.blender.org/developer/F12928071/Screen_Shot_2022-03-14_at_11.54.42_pm.jpg) ![Screen Shot 2022-03-14 at 11.54.05 pm.jpg](https://archive.blender.org/developer/F12928070/Screen_Shot_2022-03-14_at_11.54.05_pm.jpg) 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.blend](https://archive.blender.org/developer/F12929409/16-March-2022_02.49_02.blend) 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: ![Screen Shot-01.jpg](https://archive.blender.org/developer/F12929421/Screen_Shot-01.jpg) 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. ![Screen Shot 2022-03-16 at 3.23.50 am.jpg](https://archive.blender.org/developer/F12929420/Screen_Shot_2022-03-16_at_3.23.50_am.jpg) the CPU render: ![Screen Shot 2022-03-16 at 3.45.53 am.jpg](https://archive.blender.org/developer/F12929419/Screen_Shot_2022-03-16_at_3.45.53_am.jpg)
Poster

Added subscriber: @Nurb2Kea

Added subscriber: @Nurb2Kea
Nurb2Kea changed title 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. 11 months ago
Collaborator

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Collaborator

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

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

Hi, thanks for the report.

Issue is probably same as described in- #96252

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?

Hi, thanks for the report. Issue is probably same as described in- #96252 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?
Poster

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 #96252.

THX

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 #96252. THX
Collaborator

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

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

Added subscriber: @mano-wii

Added subscriber: @mano-wii
Collaborator

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

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

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.

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

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. @Nurb2Kea, could you check if the problem is really with the `Adaptive Subdivision`?
Poster

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.

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.
Collaborator

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

Changed status from 'Needs User Info' to: 'Archived'
mano-wii closed this issue 11 months ago
Collaborator

Good to know that we identified the problem.

In #96471#1324970, @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.

Good to know that we identified the problem. > In #96471#1324970, @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.
Poster

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: 42853bacc9

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: `42853bacc9`
Sign in to join this conversation.
No Label
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/ID Management
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
Interest/Python API
Interest/Render & Cycles
Interest/Render Pipeline
Interest/Sculpt, Paint & Texture
Interest/Text Editor
Interest/Translations
Interest/Triaging
Interest/Undo
Interest/USD
Interest/User Interface
Interest/UV Editing
Interest/VFX & Video
Interest/Video Sequencer
Interest/Virtual Reality
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
Module › Animation & Rigging
Module › Core
Module › Development Management
Module › Eevee & Viewport
Module › Grease Pencil
Module › Modeling
Module › Nodes & Physics
Module › Pipeline, Assets & IO
Module › Platforms, Builds, Tests & Devices
Module › Python API
Module › Render & Cycles
Module › Sculpt, Paint & Texture
Module › Triaging
Module › User Interface
Module › VFX & Video
Platform/FreeBSD
Platform/Linux
Platform/macOS
Platform/Windows
Priority › High
Priority › Low
Priority › Normal
Priority › Unbreak Now!
Status › Archived
Status › Confirmed
Status › Duplicate
Status › Needs Information from Developers
Status › Needs Information from User
Status › Needs Triage
Status › Resolved
Type › Bug
Type › Design
Type › Known Issue
Type › Patch
Type › Report
Type › To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#96471
Loading…
There is no content yet.