Page MenuHome

Segmentation fault when changing size of added objects
Closed, DuplicatePublic

Description

System Information
Operating system: Darwin-20.2.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-4.2.13

Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2021-01-01 18:07, hash: rB057a8afb879c
Worked: unknown

Short description of error
When I change the size of a just added object, Blender will crash within a few seconds.

Exact steps for others to reproduce the error
Start new file
Delete everything from scene
Shift A, add object (tested with plane, cube, uv sphere and torus)
From the popup menu, use the mouse to slowly adjust the size or radius
If you keep doing this, within a few seconds Blender will crash.

Crash log:

Event Timeline

Robert Guetzkow (rjg) changed the task status from Needs Triage to Needs Information from User.Jan 4 2021, 11:18 AM

I couldn't reproduce the problem. Could you please check if enabling Undo Legacy avoids the crash?

  1. Open the user preferences (Edit > Preferences)
  2. In the Interface tab enable Developer Extras
  3. In the Experimental tab enable Undo Legacy

If this avoids the crash it is likely the same problem as T80203.

Yes that avoids the crash.

@Wouter Stomp (wouterstomp) Could you please disable Undo Legacy, save the preferences and then try to start Blender from the terminal with the following command (path to Blender might need to be adjusted):

/Applications/Blender.app/Contents/MacOS/Blender --debug --debug-depsgraph-no-threads --threads 1 > ~/blender_debug_output.txt 2>&1

Please try if you can still make Blender crash. If it still crashes, please upload the resulting crash report and the log file blender_debug_output.txt.

Here you go:

And a crash report:

Also when running with this command, one of the times I tried Blender just locked up without a crash with the Mac spinning cursor, then I had to kill it manually.

Just to make sure that your not having an additional issue unrelated to the undo/depsgraph problem, could you please do one more test with the most recent daily build of Blender 2.92.

Same with 2.92.0 Alpha, branch: master, commit date: 2021-01-03 01:04, hash: rB1e8f2665916c

Does it also give the same stack trace or a different one (in the .crash.txt)?

No idea what to look for, but please see for yourself:

Thank you for your help. This does appear to be the same issue.