Overheating -- GPU @ 74% (macOS + AMD Radeon) #80354

Closed
opened 2020-09-02 04:49:58 +02:00 by Paul Muns · 35 comments

System Information
Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro Vega 48 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16

Blender Version
Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29
Worked: (newest version of Blender that worked as expected)

Short description of error
[Please fill out a short description of the error here]

Exact steps for others to reproduce the error
it happens every time something is selected in edit mode--even something small in number of edges like a detail in Edit Mode after hitting /.
It doesn't seem to be noticeable at first because it takes a minute to build the heat to get the fan getting louder. The thing is to watch the Activity Monitor and it immediately jumps to above 80% GPU usage with X-RAY and SOLID selected at the same time. I LOVE this mode combo and would like to use it (a thing of beauty) but my system flames out.

**System Information** Operating system: Darwin-19.6.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro Vega 48 OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.10.16 **Blender Version** Broken: version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29` Worked: (newest version of Blender that worked as expected) **Short description of error** [Please fill out a short description of the error here] **Exact steps for others to reproduce the error** it happens every time something is selected in edit mode--even something small in number of edges like a detail in Edit Mode after hitting /. It doesn't seem to be noticeable at first because it takes a minute to build the heat to get the fan getting louder. The thing is to watch the Activity Monitor and it immediately jumps to above 80% GPU usage with X-RAY and SOLID selected at the same time. I LOVE this mode combo and would like to use it (a thing of beauty) but my system flames out.
Author

Added subscriber: @PaulM44

Added subscriber: @PaulM44

#80541 was marked as duplicate of this issue

#80541 was marked as duplicate of this issue
Author

Unable to pinpoint reason. Used the same blend file in both 2.83.5 and 2.90. Within a few minutes of moving 1172 vert. subject (not huge) the fan and my SSD iMac starts getting louder and the heat starts pumping out of the back unlike anything I have experienced before. I tried to see what Activity Monitor could show as the cause, but it looks about the same in 2.83.5.
I just wanted to call it to someone's attention, Just loading this file into 2.90 and moving it around and editing doesn't seem to consistently make the heating happen. This is the first day using this version and will continue to watch for what triggers the high GPU usage. I am not using the EEVEE render mode or any image render to make this happen. VERY STRANGE-- it won't come back and be reproducible during each session. Hopefully I am the only one who notices this "ghost". Write if you want specific other info.

Unable to pinpoint reason. Used the same blend file in both 2.83.5 and 2.90. Within a few minutes of moving 1172 vert. subject (not huge) the fan and my SSD iMac starts getting louder and the heat starts pumping out of the back unlike anything I have experienced before. I tried to see what Activity Monitor could show as the cause, but it looks about the same in 2.83.5. I just wanted to call it to someone's attention, Just loading this file into 2.90 and moving it around and editing doesn't seem to consistently make the heating happen. This is the first day using this version and will continue to watch for what triggers the high GPU usage. I am not using the EEVEE render mode or any image render to make this happen. VERY STRANGE-- it won't come back and be reproducible during each session. Hopefully I am the only one who notices this "ghost". Write if you want specific other info.
Contributor

Added subscriber: @Raimund58

Added subscriber: @Raimund58
Author

Blender 2.90  @ minimized.png

Blender 2.90 Wireframe Solid.png

Two problems, one critical:

  1. When Blender 2.90 is minimized to the dock, it suddenly accelerates the Idle Wake Ups and will suddenly go to over 200.and the system starting immediately with the fan on the SSD HD computer (normally silent) suddenly getting louder and faster with generated. heat !! IF left in this state, it seems like the computer could be burned out. I had to shut off Blender to stop the process. Picture of Activity Monitor when Blender minimized and suddenly overheating system.

  2. Showing the Activity state when using Wireframe Viewport Shading Solid. When using this mode, zooming the subject in Edit mode in and out causes GPU % to jump up -- had it a 86% briefly (shown at 80%). I didn't test Object mode zooming. The mode immediately locks in at about 56% and stays there even when nothing is selected or movement happening. It doesn't release quickly with another mode selected either. This seems another more minor source of overheating. I was surprised that most other Viewport modes including EEVEE were less demanding on the system.

![Blender 2.90 @ minimized.png](https://archive.blender.org/developer/F8834265/Blender_2.90____minimized.png) ![Blender 2.90 Wireframe Solid.png](https://archive.blender.org/developer/F8834267/Blender_2.90_Wireframe_Solid.png) Two problems, one critical: 1) When Blender 2.90 is minimized to the dock, it suddenly accelerates the Idle Wake Ups and will suddenly go to over 200.and the system starting immediately with the fan on the SSD HD computer (normally silent) suddenly getting louder and faster with generated. heat !! IF left in this state, it seems like the computer could be burned out. I had to shut off Blender to stop the process. Picture of Activity Monitor when Blender minimized and suddenly overheating system. 2) Showing the Activity state when using Wireframe Viewport Shading Solid. When using this mode, zooming the subject in Edit mode in and out causes GPU % to jump up -- had it a 86% briefly (shown at 80%). I didn't test Object mode zooming. The mode immediately locks in at about 56% and stays there even when nothing is selected or movement happening. It doesn't release quickly with another mode selected either. This seems another more minor source of overheating. I was surprised that most other Viewport modes including EEVEE were less demanding on the system.
Author

See the above comments on Minimizing Blender 2.90! Very surprising. I had to add this comment because I didn't see how to change Status when I added the above.

See the above comments on Minimizing Blender 2.90! Very surprising. I had to add this comment because I didn't see how to change Status when I added the above.

Added subscriber: @iss

Added subscriber: @iss

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

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

Can you check older Blender versions and check if any of them worked better?

I also get high GPU usage, but I would say, that is normal. I don't see any abnormal resource usage when Blender is minimized, but I am also using different system.

Can you check older Blender versions and check if any of them worked better? I also get high GPU usage, but I would say, that is normal. I don't see any abnormal resource usage when Blender is minimized, but I am also using different system.
Author

Yes, I am currently using 2.83.5 with no difficulties. My problem is that I don't have adequate tools to see what is happening with the overheating with the meager Apple tools given. All I can say is that I was shocked when Minimizing to the Dock caused the system to heat and loud fan noise to increase. IF I had just left the room as normal the system could have shut down from thermal overload (I HOPE). I acted just like a render on my 2009 iMac with massive overheating except this was more immediate so I noticed it. I checked to make sure it wasn't rendering. I also checked to see if somehow I had signed up to be part of a server rendering farm (done that). I won't be using 2.90 until this "bomb" is defused. I am surprised it hasn't happened to any others yet. Almost seems like a malware, it is so unexpected.
I am also surprised that high GPU happens primarily with the Solid mode and that it requires so much more than the more refined modes or EEVEE.

Yes, I am currently using 2.83.5 with no difficulties. My problem is that I don't have adequate tools to see what is happening with the overheating with the meager Apple tools given. All I can say is that I was shocked when Minimizing to the Dock caused the system to heat and loud fan noise to increase. IF I had just left the room as normal the system could have shut down from thermal overload (I HOPE). I acted just like a render on my 2009 iMac with massive overheating except this was more immediate so I noticed it. I checked to make sure it wasn't rendering. I also checked to see if somehow I had signed up to be part of a server rendering farm (done that). I won't be using 2.90 until this "bomb" is defused. I am surprised it hasn't happened to any others yet. Almost seems like a malware, it is so unexpected. I am also surprised that high GPU happens primarily with the Solid mode and that it requires so much more than the more refined modes or EEVEE.
Author

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

Changed status from 'Needs User Info' to: 'Resolved'
Paul Muns self-assigned this 2020-09-05 02:32:51 +02:00
Author

I used 2.90 today and tried Minimizing Blender several times and nothing happened. So it is perhaps a coincidence of two processes running at the same time that were antagonistic? So far so good and I'm liking 2.9 a lot and barely had time able to see what it can do!
Thanks for your attention -- I though I had a very bad bug (not looking for attention). IF it reappears in some form that is repeatable, I be back on here.

I used 2.90 today and tried Minimizing Blender several times and nothing happened. So it is perhaps a coincidence of two processes running at the same time that were antagonistic? So far so good and I'm liking 2.9 a lot and barely had time able to see what it can do! Thanks for your attention -- I though I had a very bad bug (not looking for attention). IF it reappears in some form that is repeatable, I be back on here.
Author

Screen Shot 2020-09-09 at 10.25.02 AM.png

OK, caught it in the act this morning (see screenshot). I was using Solid with X-ray view and holding down "." to orbit around to check edit when the fan started getting louder. etc. I think it may be something to do with having both views selected at the same time. Changing from Solid to wire-frame drops the GPU usage immediately, other wise it just hangs at 86% - 92% usage until switched or computer melts..... I assume there is someone else there who is using a Mac to check this out.

![Screen Shot 2020-09-09 at 10.25.02 AM.png](https://archive.blender.org/developer/F8858671/Screen_Shot_2020-09-09_at_10.25.02_AM.png) OK, caught it in the act this morning (see screenshot). I was using Solid with X-ray view and holding down "." to orbit around to check edit when the fan started getting louder. etc. I think it may be something to do with having both views selected at the same time. Changing from Solid to wire-frame drops the GPU usage immediately, other wise it just hangs at 86% - 92% usage until switched or computer melts..... I assume there is someone else there who is using a Mac to check this out.

Changed status from 'Resolved' to: 'Needs Triage'

Changed status from 'Resolved' to: 'Needs Triage'

"There" is somebody with Mac, but chances are that their system is quite different than yours.

In #80354#1012718, @PaulM44 wrote:
OK, caught it in the act this morning (see screenshot). I was using Solid with X-ray view and holding down "." to orbit around to check edit when the fan started getting louder. etc. I think it may be something to do with having both views selected at the same time. Changing from Solid to wire-frame drops the GPU usage immediately, other wise it just hangs at 86% - 92% usage until switched or computer melts..... I assume there is someone else there who is using a Mac to check this out.

Does this happen every time? Or at least is there high chance that if you repeat this scenario, we would experience this issue?

"There" is somebody with Mac, but chances are that their system is quite different than yours. > In #80354#1012718, @PaulM44 wrote: > OK, caught it in the act this morning (see screenshot). I was using Solid with X-ray view and holding down "." to orbit around to check edit when the fan started getting louder. etc. I think it may be something to do with having both views selected at the same time. Changing from Solid to wire-frame drops the GPU usage immediately, other wise it just hangs at 86% - 92% usage until switched or computer melts..... I assume there is someone else there who is using a Mac to check this out. Does this happen every time? Or at least is there high chance that if you repeat this scenario, we would experience this issue?

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

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

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

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

Yes, now it happens every time something is selected in edit mode--even something small in number of edges like a detail in Edit Mode after hitting /.
It doesn't seem to be noticeable at first because it takes a minute to build the heat to get the fan getting louder. The thing is to watch the Activity Monitor and it immediately jumps to above 80% GPU usage with X-RAY and SOLID selected at the same time. I LOVE this mode combo and would like to use it (a thing of beauty) but my system flames out. Somehow MS systems don't have this problem.

Yes, now it happens every time something is selected in edit mode--even something small in number of edges like a detail in Edit Mode after hitting /. It doesn't seem to be noticeable at first because it takes a minute to build the heat to get the fan getting louder. The thing is to watch the Activity Monitor and it immediately jumps to above 80% GPU usage with X-RAY and SOLID selected at the same time. I LOVE this mode combo and would like to use it (a thing of beauty) but my system flames out. Somehow MS systems don't have this problem.

Added subscribers: @ankitm, @sebbas

Added subscribers: @ankitm, @sebbas

@ankitm, @sebbas If I remember correctly you have mac machine. Can you check this out?

@ankitm, @sebbas If I remember correctly you have mac machine. Can you check this out?
Member

I'll check it soon but noting another report here: #80541 (Solid View -->>Thermal Overload)
I don't have Radeon Pro Vega 48, just an Intel HD 6000.

I'll check it soon but noting another report here: #80541 (Solid View -->>Thermal Overload) I don't have Radeon Pro Vega 48, just an Intel HD 6000.
Contributor

@ankitm The author is also @PaulM44 on #80541: Solid View -->>Thermal Overload

@ankitm The author is also @PaulM44 on #80541: Solid View -->>Thermal Overload
Author

A clue is that there is no problem with version 2.83.5 (using same blend file too) with this combination of views and I was only able to get the GPU up to 50% with a lot of moving around but then it dropped back immediately when I stopped to zero. Some code difference in 2.90 is causing the GPU to jump to 80%+ and hang there regardless of movement.
I have notified Apple about the problem as well -- whatever the code is, it could be "dangerous" for the way OSX is dealing with it.....

A clue is that there is no problem with version 2.83.5 (using same blend file too) with this combination of views and I was only able to get the GPU up to 50% with a lot of moving around but then it dropped back immediately when I stopped to zero. Some code difference in 2.90 is causing the GPU to jump to 80%+ and hang there regardless of movement. I have notified Apple about the problem as well -- whatever the code is, it could be "dangerous" for the way OSX is dealing with it.....
Author

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Author

This comment was removed by @PaulM44

*This comment was removed by @PaulM44*
Author

Changed status from 'Resolved' to: 'Archived'

Changed status from 'Resolved' to: 'Archived'
Author

I tried 2.91 alpha and thought it didn't have the problem but finally, it sent the GPU to 92% and just hung with no screen movement. So unfortunately it has yet to be resolved. ( I added a message before that it was resolved but found it isn't.)

I tried 2.91 alpha and thought it didn't have the problem but finally, it sent the GPU to 92% and just hung with no screen movement. So unfortunately it has yet to be resolved. ( I added a message before that it was resolved but found it isn't.)
Author

What is Invalid is that the issue is resolved--not so fast! Invalid means the same as Resolved? And Normal means all is fine? The labels need a little more clarification.....

What is Invalid is that the issue is resolved--not so fast! Invalid means the same as Resolved? And Normal means all is fine? The labels need a little more clarification.....

Added subscriber: @rjg

Added subscriber: @rjg

Changed status from 'Archived' to: 'Needs Triage'

Changed status from 'Archived' to: 'Needs Triage'

@PaulM44 Invalid means that the ticket is closed because it's not a valid bug report. Resolved is for when a confirmed bug report has been resolved. Please read the Triaging Playbook for more information.

@PaulM44 *Invalid* means that the ticket is closed because it's not a valid bug report. *Resolved* is for when a confirmed bug report has been resolved. Please read the [Triaging Playbook ](https://wiki.blender.org/wiki/Process/Bug_Reports/Triaging_Playbook) for more information.
Campbell Barton changed title from Overheating -- GPU @ 74% to Overheating -- GPU @ 74% (macOS + AMD Radeon) 2020-09-12 02:58:21 +02:00
Author

Thank you Robert for reopening. I dearly need that view option to do effective Modeling and every time I click onto it I can hear the fan starting to work faster and heat starting to accumulate. I can't believe no one else has had this problem or perhaps doesn't recognize the cause. I am adding this message because I am using 2.91alpha and it has the same problem. I will continue to download and use the latest experimental version to see if anything has changed.

Thank you Robert for reopening. I dearly need that view option to do effective Modeling and every time I click onto it I can hear the fan starting to work faster and heat starting to accumulate. I can't believe no one else has had this problem or perhaps doesn't recognize the cause. I am adding this message because I am using 2.91alpha and it has the same problem. I will continue to download and use the latest experimental version to see if anything has changed.
Author

I just got the latest build: Blender-2.91.0-099ce95ef36d-macOS. I discovered that in LAYOUT mode this doesn't happen. It only happens in MODELING mode and it happens every time. Modeling mode hates my GPU and will overheat it into a molten mass if left un-aware, No overheating while Editing in Layout mode. Hint Hint.

I just got the latest build: Blender-2.91.0-099ce95ef36d-macOS. I discovered that in LAYOUT mode this doesn't happen. It only happens in MODELING mode and it happens every time. Modeling mode hates my GPU and will overheat it into a molten mass if left un-aware, No overheating while Editing in Layout mode. Hint Hint.
Author

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Author

No longer a problem since 2.91. Resolved for now. Paul

No longer a problem since 2.91. Resolved for now. Paul
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
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
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 Info 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
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#80354
No description provided.