Solid View -->>Thermal Overload #80541

New Issue

Paul Muns · 2020-09-07T01:06:03+02:00

Paul Muns commented

2020-09-07 01:06:03 +02:00

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
[Please describe the exact steps needed to reproduce the issue]
[Based on the default startup or an attached .blend file (as simple as possible)]

**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** [Please describe the exact steps needed to reproduce the issue] [Based on the default startup or an attached .blend file (as simple as possible)]

Paul Muns commented

2020-09-07 01:06:03 +02:00

Added subscriber: @PaulM44

Paul Muns commented

2020-09-07 01:24:12 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Paul Muns commented

2020-09-07 01:24:12 +02:00

HorseSaddle2.blend

Explanation PNG file and actual Blend file attached. I have reproduced this 3 times today and feel satisfied that it should be quickly repeatable. This is the problem that I reported a few days ago but couldn't repeat -- other than a clear sense that the Solid view was somehow sucking up more resources and a problem.
I checked this by selecting the two objects and either already being in Solid view ( or switching into Solid after going in Edit) and then going into Edit Mode and waiting about 10 seconds for the fan to start revving. I then clicked back to wire frame or any other view to stop the overload. HEAT starts belching out of the back right away so be careful.
I don't know what the upper limit of vertices is for this computer--perhaps I have exceeded that limit except that there is no problem with any other view so far.....
Paul

![Thermal Meltdown.png](https://archive.blender.org/developer/F8848492/Thermal_Meltdown.png) [HorseSaddle2.blend](https://archive.blender.org/developer/F8848499/HorseSaddle2.blend) Explanation PNG file and actual Blend file attached. I have reproduced this 3 times today and feel satisfied that it should be quickly repeatable. This is the problem that I reported a few days ago but couldn't repeat -- other than a clear sense that the Solid view was somehow sucking up more resources and a problem. I checked this by selecting the two objects and either already being in Solid view ( or switching into Solid after going in Edit) and then going into Edit Mode and waiting about 10 seconds for the fan to start revving. I then clicked back to wire frame or any other view to stop the overload. HEAT starts belching out of the back right away so be careful. I don't know what the upper limit of vertices is for this computer--perhaps I have exceeded that limit except that there is no problem with any other view so far..... Paul

Paul Muns changed title from ~~So;id View -->>Thermal Overload~~ to Solid View -->>Thermal Overload

2020-09-07 01:24:57 +02:00

Ankit Meel commented

2020-09-07 23:13:45 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2020-09-07 23:13:45 +02:00

I opened the file and it was in shading mode. It took a while for shader compilation while the GPU was busy. Then everything became normal, memory ~350MB, CPU ~7% and GPU idle. Switched to solid mode and the CPU/memory activity is still the same. GPU is also idle unless I move the object, which is expected.

There's nothing out of ordinary. You can check Activity monitor > window menu > GPU history to see if GPU is working. Check the temperature using Intel Power Gadget. Below 95 C seems to be fine.

Darwin 18, Intel HD 6000.

I opened the file and it was in shading mode. It took a while for shader compilation while the GPU was busy. Then everything became normal, memory ~350MB, CPU ~7% and GPU idle. Switched to solid mode and the CPU/memory activity is still the same. GPU is also idle unless I move the object, which is expected. There's nothing out of ordinary. You can check Activity monitor > window menu > GPU history to see if GPU is working. Check the temperature using Intel Power Gadget. Below 95 C seems to be fine. Darwin 18, Intel HD 6000.

Ankit Meel commented

2020-09-07 23:48:34 +02:00

Changed status from 'Needs Developer To Reproduce' to: 'Needs User Info'

Ankit Meel commented

2020-09-07 23:48:34 +02:00

Could you check Activity monitor and see what is using CPU/GPU ?

Paul Muns commented

2020-09-08 02:54:49 +02:00

I also continued working with the same file and can't get it to repeat the overheating this afternoon. It happened this yesterday morning 3 times and has ghosted me two other times. Perhaps it's just the particular brief activity / setup I have going that sets the process in motion. I have been using EEVEE occasionally and that shows little if any activity in the CPU and none in the GPU. The SOLID view, doesn't show much that would indicate the overload although I don't have time to turn on Activity Monitor before shutting down the overload--it's that fast when it happens.
I assume I am the only one to experience this and will assume that it too shall go away with the constant Blender updates. I really thought I had it nailed. If no one else finds it in a week then mark this "resolved" again and I'll just be careful until I can get a few versions newer.....
Thanks Ankit for the effort!

I also continued working with the same file and can't get it to repeat the overheating this afternoon. It happened this yesterday morning 3 times and has ghosted me two other times. Perhaps it's just the particular brief activity / setup I have going that sets the process in motion. I have been using EEVEE occasionally and that shows little if any activity in the CPU and none in the GPU. The SOLID view, doesn't show much that would indicate the overload although I don't have time to turn on Activity Monitor before shutting down the overload--it's that fast when it happens. I assume I am the only one to experience this and will assume that it too shall go away with the constant Blender updates. I really thought I had it nailed. If no one else finds it in a week then mark this "resolved" again and I'll just be careful until I can get a few versions newer..... Thanks Ankit for the effort!

Ankit Meel commented

2020-09-08 08:14:22 +02:00

I'd guess that some other background process like Spotlight was busy at the same time as Blender. but that won't explain the repeatability thrice.
Do you have multiple GPUs ?

although I don't have time to turn on Activity Monitor before shutting down the overload

I keep it open all the times with dock icon showing CPU usage.

I'd guess that some other background process like Spotlight was busy at the same time as Blender. but that won't explain the repeatability thrice. Do you have multiple GPUs ? > although I don't have time to turn on Activity Monitor before shutting down the overload I keep it open all the times with dock icon showing CPU usage. ![image.png](https://archive.blender.org/developer/F8853245/image.png)

Paul Muns commented

2020-09-08 19:53:41 +02:00

Yes, I'll keep Activity Monitor on all the time using 2.9 now. I only have the one GPU:
Radeon Pro Vega 48:

Chipset Model:	Radeon Pro Vega 48
Type:	GPU
Bus:	PCIe
PCIe Lane Width:	x16
VRAM (Total):	8 GB
Vendor:	AMD (0x1002)
Device ID:	0x6869
Revision ID:	0x0000
ROM Revision:	113-D0650E-072
VBIOS Version:	113-D05001A1XG-011
Option ROM Version:	113-D05001A1XG-011
EFI Driver Version:	01.01.072
Metal:	Supported, feature set macOS GPUFamily2 v1
Displays:

iMac:

Display Type:	Built-In Retina LCD
Resolution:	5120 x 2880 Retina
Framebuffer Depth:	30-Bit Color (ARGB2101010)
Main Display:	Yes
Mirror:	Off
Online:	Yes
Automatically Adjust Brightness:	No
Connection Type:	Internal

...so it has to be either the CPU or GPU overheating I assume ... I've seen the GPU jump to 92% briefly. IF no one else has experienced this (I'm surprised) then it must be a quirk of the current OSX environment (with the event cascading) that is the cause and MS is saved (this time ; > }}

Yes, I'll keep Activity Monitor on all the time using 2.9 now. I only have the one GPU: Radeon Pro Vega 48: ``` Chipset Model: Radeon Pro Vega 48 Type: GPU Bus: PCIe PCIe Lane Width: x16 VRAM (Total): 8 GB Vendor: AMD (0x1002) Device ID: 0x6869 Revision ID: 0x0000 ROM Revision: 113-D0650E-072 VBIOS Version: 113-D05001A1XG-011 Option ROM Version: 113-D05001A1XG-011 EFI Driver Version: 01.01.072 Metal: Supported, feature set macOS GPUFamily2 v1 Displays: ``` iMac: ``` Display Type: Built-In Retina LCD Resolution: 5120 x 2880 Retina Framebuffer Depth: 30-Bit Color (ARGB2101010) Main Display: Yes Mirror: Off Online: Yes Automatically Adjust Brightness: No Connection Type: Internal ``` **** ...so it has to be either the CPU or GPU overheating I assume ... I've seen the GPU jump to 92% briefly. IF no one else has experienced this (I'm surprised) then it must be a quirk of the current OSX environment (with the event cascading) that is the cause and MS is saved (this time ; > }}

Ankit Meel commented

2020-09-11 10:14:48 +02:00

Closed as duplicate of #80354

Ankit Meel closed this issue

2020-09-11 10:14:48 +02:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Solid View -->>Thermal Overload #80541