I was able to compile Blender and then bisect.

I think your node "image texture" on which you are trying to bake the texture is already connected to your material output, bake your lightning first with yout material connected to your material output, then connect your image texture to your material output, I had the same issue and it worked

Mine is on a Mac Studio (M1 Max 32GB), short clip of the flickering in the (now merged) T98762

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

I also have a flickering UI on Macbook Pro 16" M1 Max - Blender Version 3.2.0

@Julian Eisel (Severin) hi, your hardware and OS matches with the affected systems (mentioned in the report description)
Can you reproduce this issue?

Same issue here, on Macbook M1 Pro -> flickering in Wire more and Shaded mode. Was present in 3.1, and is still present in 3.2.
Does not happen on Nvidia RTX2017 PC build -> tested the same thing, but on the external screen for the PC, and no such flickering.

In mi case I think the issue is not related with the hardware and the macOS. With the same hardware (iMac i7 27” mid 2011, AMD Radeon HD 6970M 2GB, RAM 32 GB) and macOS 10.13.6 the hair particles are displayed correctly in viewport (Object Mode > Solid Shade) on Blender 3.0 but with Blender 3.1 & 3.2 the issue appears.

@Corwin Kerr (ckerr) Is this still an issue?
I can not reproduce the issue with neither 3.2 nor current master branch on MacPro with AMD W6800X card.

Ok, will close then.
Thanks again for the report :)

谢谢lijia，谢谢blender的开发人员，问题已经解决了，3.2的stable版本可以了
Thanks lija and developers of blender！
This problem has been resolvede in verion 3.2 stabel (2022.6.14 daily build)

@lijia (togaga) and @liuyong (liuyong) hi, could you both please use translated text?
@liuyong (liuyong), does this problem remain in recent 3.2 release for you?

使用的是2022.6.14 daily build 的3.2 stable版本吗？

尝试了最新的2022.6.14 daily build版本，
并且这次没有直接用F12渲染，
而是先用视图的实时渲染模式，渲染引擎改为Cycles GPU，
然后看到左上角提示正在启动引擎内核（第一次启动需要几分钟），
于是这次等了大概3~4分钟，期间鼠标没有变成无限“loading”图标，最后Gpu实时渲染成功，之后再F12渲染也成功。
速度也确实快了很多。

Thanks for info, seems to be same as T96949 then, so will merge.

Blender still reports memory wrong. I will add a demo file when I have time. For now, here is a screenshot. In it, you can see Blender thinks the most memory it's used is 3002 MB, when it is currently using ~12 GB.

A lot of development has happened since I opened this issue. I will try to prepare a demo file to see if I can reproduce this. Apologies for the late reply.

The problem is still there with Blender Version 3.2.0 (3.2.0 2022-06-08) on Macos 10.13.6.

today i update my mac os to 10.15.7 and try use blender 3.2

Ok, found I was having a mixture of Monterey and Ventura toolchains in the compilation. After making sure that only the Ventura toolchain is used for compilation, the issue went away,.

I'm not sure if the steps are clear.
Click and Drag in the viewport activates the select box (as expected).
Maybe it's due to a different version of drivers?

@Germano Cavalcante (mano-wii) can you check?

This seems identical to T96133, so merging.

Hi,
I'm also experiencing this issue on a M1 Ultra Mac Studio.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Too many layers of abstraction, I need to learn more about the app architecture.

@Panos Pagonis (pan.noise) Metal is only supported in Cycles compute, but the crashes happen while drawing the viewport in your case, similar to this report, that's why I merged it. So it is probably coincidentally than a direct cause.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Running the test file on 3.1.2, I found that Blender quits after ~30 seconds of freezing the OS instead of requiring a hard reset. Still, no crash log is saved.
The only information I was able to get was the following output from the terminal:

I tried to get a crash report to provide you with the stacktrace, but unfortunately as this bug freezes the entire MacOS the crash report is not saved at all. If you have any suggestions how I could provide you with more detailed/useful information, please let me know.