Page MenuHome

Grease Pencil crashes in 32-Bit version
Open, Confirmed, MediumPublic


System Information
Operating system: win 7
Graphics card: Vega 64
Full System Information: Here

Blender Version
Broken: -69b2f5268114-windows32
Works: -69b2f5268114-windows64

Short description of error

32-Bit Blender crashes when drawing with grease pencil.

Exact steps for others to reproduce the error

  • Open Blender
  • New --> 2D Animation

At which point I get this:

  • Select a brush and start drawing
  • Switch to eraser and crash

This file was saved in the 32-bit version:

Open and start drawing and erasing.

Here's the log from --debug --factory-startup

location: <unknown location>:-1
Traceback (most recent call last):
  File "N:\Temp\Blender\blender-2.80.0-git.69b2f5268114-windows32\2.80\scripts\startup\bl_ui\", line 94, in draw
  File "N:\Temp\Blender\blender-2.80.0-git.69b2f5268114-windows32\2.80\scripts\startup\bl_ui\", line 119, in draw_left
    draw_fn(context, layout, tool)
  File "N:\Temp\Blender\blender-2.80.0-git.69b2f5268114-windows32\2.80\scripts\startup\bl_ui\", line 353, in PAINT_GPENCIL
  File "N:\Temp\Blender\blender-2.80.0-git.69b2f5268114-windows32\2.80\scripts\startup\bl_ui\", line 323, in draw_color_selector
    ma = gp_settings.material
AttributeError: 'NoneType' object has no attribute 'material'



Event Timeline

Jacques Lucke (JacquesLucke) triaged this task as Confirmed, Medium priority.Mon, Feb 11, 2:23 PM

I get an assert when I open this file. Bisecting...

@Jacques Lucke (JacquesLucke) I got to open it get the assert. The problem is related to brushes. They have forgotten the gp_settings... I'm investigating.

The eraser brush is damaged and the same for the default draw brush.

I going to do some changes to avoid crashes if the brush is damaged, but we need to know how the brush was damaged.

@Christopher Anderssarian (Christopher_Anderssarian) Could you tell us the steps you did with the brushes to get this situation? did you have any other crash before?

Okay, new update, I had been running with --debug (I'm having the same problems as reported in T60089 and with debug is the only way to run Blender)
For some spontaneous reason, Blender* launched (without the debug command)
Here's what I found:
Launching Blender's 32-Bit & 64-Bit build (-69b2f5268114-) both with --debug --factory-startup show different results:


*(At least with Correction: -7f77961f1c38-windows32 it did, I haven't managed to get -69b2f5268114-windows32 running without --debug)

69b2f5268114-windows32 has brush damaged... maybe it's the template.