Page MenuHome

Working with curves crashes Blender 2.8
Closed, ResolvedPublic


System Information
macOS 10.13.6 / Radeon Pro 460 4096 MB

Blender Version
Broken: 2.8 alpha
Worked: 2.8 pre-alpha

Short description of error
Blender crashes every time I add or duplicate a curve.

Exact steps for others to reproduce the error

  • open Blender
  • add curve
  • crash

Event Timeline

Bastien Montagne (mont29) triaged this task as Needs Information from User priority.Jul 17 2018, 4:46 PM

Cannot confirm that here on linux (debian64 testing), with latest blender2.8 branch. Please either retry with next available build (iirc, OS X builds are on hold currently due to changing the buildbot), and/or provide more info on how to reproduce the issue (like draw mode you are using, etc. - that’s why we always request a .blend file!).

I just built Blender 2.8 on my machine (MacBookPro 15'' 2017) and tested the latest version.
Adding a curve still crashes Blender.
On my other machine (win64) Blender 2.8 works great. It's only happening on macOS.
Here is my error report:

Process: blender [3534]
Path: /Users/USER/*/
Identifier: org.blenderfoundation.blender
Version: 2.80 (2.80 2018-07-17, Blender Foundation)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: blender [3534]
User ID: 501

Date/Time: 2018-07-17 16:51:38.876 +0200
OS Version: Mac OS X 10.13.6 (17G65)
Report Version: 12
Bridge OS Version: 3.0 (14Y664)
Anonymous UUID: A0D8A34D-C4EF-E805-3AF9-73A2CEB4F14A

Time Awake Since Boot: 5200 seconds

System Integrity Protection: enabled

Crashed Thread: 0 Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0:
__TEXT 000000010279d000-0000000107f81000 [ 87.9M] r-x/rwx SM=COW /Users/USER/*/

Thread 0 Crashed:: Dispatch queue:
0 org.blenderfoundation.blender 0x0000000102e5e3fb DRW_displist_indexbuf_calc_triangles_in_order_split_by_material + 91
1 org.blenderfoundation.blender 0x0000000102e5d91b DRW_curve_batch_cache_get_surface_shaded + 347
2 org.blenderfoundation.blender 0x0000000102ea2f6f workbench_deferred_solid_cache_populate + 1167
3 org.blenderfoundation.blender 0x0000000102e72fef DRW_draw_render_loop_ex + 959
4 org.blenderfoundation.blender 0x00000001029c7c1c view3d_main_region_draw + 124
5 org.blenderfoundation.blender 0x0000000102bd93cc ED_region_do_draw + 396
6 org.blenderfoundation.blender 0x00000001028dceb6 wm_draw_update + 1526
7 org.blenderfoundation.blender 0x00000001028db040 WM_main + 48
8 org.blenderfoundation.blender 0x00000001028d708c main + 972
9 libdyld.dylib 0x00007fff56eee015 start + 1

Here is my StartUp-blend-file:

I hope this helps figuring out, what's wrong.

Carsten Peter Kraushaar (carpe23) raised the priority of this task from Needs Information from User to Normal.Jul 17 2018, 5:23 PM
Christopher Anderssarian (Christopher_Anderssarian) raised the priority of this task from Normal to Needs Triage by Developer.Jul 17 2018, 6:27 PM

I can replicate on this configuration:

Windows 10 Pro 64 bit (1803)
AMD Radeon RX480 4GB with Radeon Software 18.7.1
Blender 2.8 Alpha a28fd8fee2f

Just doing this causes Blender to crash on my configuration:

  1. Load factory settings
  2. Shift-A -> Add Curve -> Bezier

Probably significant information: this does not seem limited to curves, but also Nurbs surfaces, Metaballs and Text, i.e. any geometry object that is not a 3D mesh.

I can replicate on:

macOS High Sierra, Version 10.13.6

MacBook Pro (Retina, 15-inch, Mid 2015)

Latest Blender version compiled from blender2.8 branch


  1. Open Blender through terminal
  2. Load Factory Settings
  3. Add any Curve, object, or append or link any curve object

Crash Reports:


*System Report*

EDIT: moved reports to pastebin

On the latest Blender 2.80 local build on Windows 10 64bit 8a42b3909f3 I found that while I cannot create them without the program crashing, I can display and tweak Curves and Text created under 2.79, but not Surfaces. Here is an attached file to quickly test this, made with Blender 2.79.

Bastien Montagne (mont29) triaged this task as Normal priority.

Looks like a drawing code issue, @Jeroen Bakker (jbakker) mind checking on that one? Thanks.