Blender 4.0.1 edit mode completely freezing/crashing application for even simple topology #115784

New Issue

Delia-M · 2023-12-05T06:06:52+01:00

Delia-M commented

2023-12-05 06:06:52 +01:00

System Information
Operating system: MacOS-13.2.1-X86_64 x86_64 64 bit
Graphics card: Intel Iris Plus Graphics 1536 MB (lmao)
CPU: 2 GHz Quad-Core Intel Core i5

Blender Version
Broken: 4.0.1, branch: main, commit date: 2023
4.0.1, branch: blender-v4.0-release, commit date: 2023-11-17 02:07, hash: d0dd92834a
Worked: 3.6

Short description of error
Trying to switch to edit mode and interact with any object at all seems to spike the CPU and freeze the program (see first screenshot below, there were only 2 objects in the scene and the background should be the default dark gray not white). Can only quit the program via the command line. Happens even when using primitives. Texturing, geo nodes, object mode, rendering, and compositing all work fine. I don't have a large asset library and it's not an addon. I've also noticed that small artifacts are popping up on meshes in solid view (2nd & 3rd screenshots) although they don't appear in renders. They seem to show up no matter what and are unrelated to any topology issues. Hoping this isn't a hardware issue on my end.

Exact steps for others to reproduce the error
Try to use edit mode (on my computer)

**System Information** Operating system: MacOS-13.2.1-X86_64 x86_64 64 bit Graphics card: Intel Iris Plus Graphics 1536 MB (lmao) CPU: 2 GHz Quad-Core Intel Core i5 **Blender Version** Broken: 4.0.1, branch: main, commit date: 2023 4.0.1, branch: blender-v4.0-release, commit date: 2023-11-17 02:07, hash: d0dd92834a08 Worked: 3.6 **Short description of error** Trying to switch to edit mode and interact with any object at all seems to spike the CPU and freeze the program (see first screenshot below, there were only 2 objects in the scene and the background should be the default dark gray not white). Can only quit the program via the command line. Happens even when using primitives. Texturing, geo nodes, object mode, rendering, and compositing all work fine. I don't have a large asset library and it's not an addon. I've also noticed that small artifacts are popping up on meshes in solid view (2nd & 3rd screenshots) although they don't appear in renders. They seem to show up no matter what and are unrelated to any topology issues. Hoping this isn't a hardware issue on my end. **Exact steps for others to reproduce the error** Try to use edit mode (on my computer)

Screenshot 2023-12-05 at 12.01.58 AM.png

833 KiB

Screenshot 2023-12-04 at 7.29.04 PM.png

546 KiB

Screenshot 2023-12-04 at 7.29.40 PM.png

958 KiB

Screenshot 2023-12-05 at 12.01.58 AM.png

Delia-M added the

labels 2023-12-05 06:06:53 +01:00

Delia-M commented

2023-12-05 06:08:24 +01:00

screenshots are out of order but it's pretty self-explanatory

Philipp Oeser commented

2023-12-05 10:06:14 +01:00

From https://www.blender.org/download/requirements/ :

Intel: macOS version 10.15 or newer (AMD GPU or Intel Skylake and above)

Looks like your system should be supported

@Michael-Jones : does this ring a bell?

From https://www.blender.org/download/requirements/ : > Intel: macOS version 10.15 or newer (AMD GPU or Intel Skylake and above) Looks like your system should be supported @Michael-Jones : does this ring a bell?

Philipp Oeser added the

Platform

macOS

label 2023-12-05 10:27:28 +01:00

Pratik Borhade commented

2023-12-06 06:54:37 +01:00

Hi, does this happen after factory reset?: File > Defaults > Load Factory Settings
re artifacts: do they remain after tweaking the clip values?

Intel Iris Plus Graphics 1536 MB

Does it mean your device has 1536 mb of VRAM? which is less than minimum requirement

@lichtwerk , wrong Michael :) (for viewport metal backend Michael-Parkin-White-Apple)

Hi, does this happen after factory reset?: `File > Defaults > Load Factory Settings` re artifacts: do they remain after tweaking the clip values? > Intel Iris Plus Graphics 1536 MB Does it mean your device has 1536 mb of VRAM? which is less than minimum requirement @lichtwerk , wrong Michael :) (for viewport metal backend `Michael-Parkin-White-Apple`)

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2023-12-06 06:54:47 +01:00

Delia-M commented

2023-12-06 07:40:28 +01:00

Factory reset doesn't solve the issue. Changing the clip values does seem to affect/partly reduce the artifacts but doesn't completely get rid of them. I'm rendering on my CPU and as I mentioned, this hasn't given me any problems (in Cycles at least). 3.6 ran alright, but I can't find the exact requirements for it on the Blender website anymore. From what little I know edit mode operations should be running on the CPU; could a VRAM issue cause this and no other major problems? I tend to work with texturing and geonodes, so I had a few days of using 4.01 before I to model something. Thanks for your help.

Pratik Borhade commented

2023-12-06 09:42:59 +01:00

Maybe some intel specific problem (We haven't received any similar report so far, AFAIK).
Unfortunately, I don't have hardware to verify the problem. Also: We may require .blend file if artifacts/white background is appearing in specific file.
cc @Michael-Parkin-White-Apple

Maybe some intel specific problem (We haven't received any similar report so far, AFAIK). Unfortunately, I don't have hardware to verify the problem. Also: We may require .blend file if artifacts/white background is appearing in specific file. cc @Michael-Parkin-White-Apple

Delia-M commented

2023-12-06 21:02:46 +01:00

I'd be happy to provide a file but it's happening no matter what. I've also found 1 other person with this problem on Reddit with nearly identical hardware.

[(https://www.reddit.com/r/blenderhelp/comments/186vl4w/beginner_having_issues/kbv1w4j/?context=3)]

I'd be happy to provide a file but it's happening no matter what. I've also found 1 other person with this problem on Reddit with nearly identical hardware. [(https://www.reddit.com/r/blenderhelp/comments/186vl4w/beginner_having_issues/kbv1w4j/?context=3)]

Todd-Keller commented

2023-12-07 00:28:18 +01:00

Running into the same issue on Windows 11 Pron, Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz 2.29 GHz (2 processors), 128 GB RAM, Nvidia Quadro

Pratik Borhade added

Status

Needs Triage

and removed

Status

Needs Information from User

labels 2023-12-07 04:09:03 +01:00

Michael Parkin-White commented

2023-12-10 18:06:51 +01:00

System should be supported, but this sounds like an issue may be on the CPU side. While the OpenGL backend was removed in Blender 4.0, most users would have been running the Metal backend in 3.6 as well, unless explicitly switching.

Without crash logs, this may be a little tricky to diagnose, as the change set for 4.0 is fairly large, and this is also a fairly simple repro case. I'd be curious if it would be possible to get a crash log from force quitting the application while it is in a frozen state, this would ultimately tell us which threads are active and where the app may be stuck.

System should be supported, but this sounds like an issue may be on the CPU side. While the OpenGL backend was removed in Blender 4.0, most users would have been running the Metal backend in 3.6 as well, unless explicitly switching. Without crash logs, this may be a little tricky to diagnose, as the change set for 4.0 is fairly large, and this is also a fairly simple repro case. I'd be curious if it would be possible to get a crash log from force quitting the application while it is in a frozen state, this would ultimately tell us which threads are active and where the app may be stuck.

Pratik Borhade added

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Blender 4.0.1 edit mode completely freezing/crashing application for even simple topology #115784