GreasePencil: Modifying name of new color in new palette segfaults #50123

New Issue

Folkert de Vries · 2016-11-27T00:15:11+01:00

Folkert de Vries commented

2016-11-27 00:15:11 +01:00

System Information
Linux Mint (Ubuntu)

Blender Version
Broken: 2.78 729affe

Short description of error
Grease Pencil Palettes are not linked to the scene, renaming their colors' names segfaults

Exact steps for others to reproduce the error

open a fresh blend file
create a new grease pencil data block (or "New Layer", doesn't change the result)
crucial fact is that there is no palette linked to the grease pencil data-block
paste the following two lines into the console

scene = bpy.context.scene
palette = scene.grease_pencil.palettes.active or scene.grease_pencil.palettes.new("GP_Palett")

observe how the newly created palette is not visible in the UI
change the name of a color by executing

mycolor = palette.colors.new()

# this expression segfaults
mycolor.name = "test"

Crucially, changing the hide property doesn't segfault, so name seems to be special.

This segfault is probably only possible via scripting, but still very bad. It was discovered during my work on the Freestyle GPencil Exporter.

**System Information** Linux Mint (Ubuntu) **Blender Version** Broken: 2.78 729affe **Short description of error** Grease Pencil Palettes are not linked to the scene, renaming their colors' names segfaults **Exact steps for others to reproduce the error** * open a fresh blend file * create a new grease pencil data block (or "New Layer", doesn't change the result) * crucial fact is that there is no palette linked to the grease pencil data-block * paste the following two lines into the console ``` scene = bpy.context.scene palette = scene.grease_pencil.palettes.active or scene.grease_pencil.palettes.new("GP_Palett") ``` * observe how the newly created palette is not visible in the UI * change the name of a color by executing ``` mycolor = palette.colors.new() # this expression segfaults mycolor.name = "test" ``` Crucially, changing the `hide` property doesn't segfault, so `name` seems to be special. This segfault is probably only possible via scripting, but still very bad. It was discovered during my work on the Freestyle GPencil Exporter.

Folkert de Vries commented

2016-11-27 00:15:11 +01:00

Changed status to: 'Open'

Folkert de Vries commented

2016-11-27 00:15:11 +01:00

Added subscriber: @flokkievids

Joshua Leung commented

2016-11-27 00:40:46 +01:00

Added subscriber: @JoshuaLeung

Joshua Leung commented

2016-11-27 00:40:46 +01:00

Actually, even just trying to print the mycolor variable (before changing the name) caused a crash in current master.

I previously fixed a bug where this was crashing because a name-setting function here needed the owner-datablock, but that wasn't supplied when accessing this stuff from the context.

Actually, even just trying to print the `mycolor` variable (before changing the name) caused a crash in current master. I previously fixed a bug where this was crashing because a name-setting function here needed the owner-datablock, but that wasn't supplied when accessing this stuff from the context.

blender-admin commented

2016-11-27 14:28:12 +01:00

This issue was referenced by e2d223461e

This issue was referenced by e2d223461efeea4792defb254c692828266478d1

Joshua Leung commented

2016-11-27 14:35:54 +01:00

Changed status from 'Open' to: 'Resolved'

Joshua Leung closed this issue

2016-11-27 14:35:54 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

GreasePencil: Modifying name of new color in new palette segfaults #50123