Page MenuHome

Clicking menus causes Mac to freeze entirely
Open, Waiting for Developer to ReproducePublic


System Information
Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce 320M OpenGL Engine NVIDIA Corporation 3.3 NVIDIA-10.4.14 310.90.30.05b27

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-24 14:22, hash: rB507ffee6e1f4
Worked: (optional)

Short description of error
While clicking/hovering on the various menus - none in particular, but mostly the bottom-right menu ones - the computer will freeze, with no possibility of moving cursor, and keyboard shortcuts of any sort won't work. This freeze status sometimes lasts for a few seconds, sometimes for several seconds. At times it won't "de-freeze", so i have to force shut down my Mac.
Lastly, this happens regardless how much the cpu is working. I could simply start a new project, single cube in the center, and clicking on the menu and icons will reproduce the bug.



Related Objects

Event Timeline

IMO your workstation not meet minimum Blender requirements, you can check here

GeForce 320M have older GPU architecture, minimum requirement is Tesla GPU architecture

But it makes no sense. It can render an animation, but it freezes on menus. It's obviously a bug.

William Reynish (billreynish) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Jul 29 2019, 12:16 AM

You'll have to explain what you mean by "the bottom-right menu ones".

You've circled the Properties editor. Which menu are you referring to that causes Blender to crash?

As i said in the bug report, there is no specific button-link that if selected will reproduce the bug. I just noticed that the Properties editor is the area where the computer starts to freeze more often. But - although less often - it also happens while doing any sort of operation.

William Reynish (billreynish) raised the priority of this task from Needs Information from User to Waiting for Developer to Reproduce.Jul 29 2019, 12:43 PM

Okay, then it's a bit hard to debug probably. It could be something with your system or drivers.