Error spam in console when opening file from 2.7x #75318

New Issue

Stellarator Tokamak · 2020-04-02T21:04:44+02:00

2020-04-02 21:04:44 +02:00

System Information
Operating system: Windows 10
Graphics card: GeForce GTX 1080

Blender Version
Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-04-01 17:35, hash: a9963669f9, type: Release, uild date: 2020-04-02, 06:54:40
Worked: 2.79b

Many of my files created in 2.7x often spam the console with the following error when opened in 2.8x:

write_customdata error: layer '':15 - can't be written to file

Where '15' can be other numbers. Sometimes dozens of times whenever whatever is throwing this error updates, such as on a frame change, and blender is momentarily unresponsive.

I've found that through process of elimination by deleting data, and I've tracked down a specific example of a mesh data block that triggers the error so you can repro. Deleting the object does not stop the error, but deleting the mesh data immediately does.

I can't stress enough that this normally applies to dozens of objects in a complex file like a rigged character, so tracking down each one is a long process during which blender is extremely laggy.

Repro steps:
Open attatched .blend file, open console, and change the current frame. Since I've only kept one piece of mesh data that causes it, you should see the error once per frame change.

Note: For some reason, switching into and out of edit mode also stops the error, but this isn't always practical in a complex file with hundreds or thousands of objects.

customdata error.blend

**System Information** Operating system: Windows 10 Graphics card: GeForce GTX 1080 **Blender Version** Broken: version: 2.83 (sub 11), branch: master, commit date: 2020-04-01 17:35, hash: a9963669f9d2, type: Release, uild date: 2020-04-02, 06:54:40 Worked: 2.79b Many of my files created in 2.7x often spam the console with the following error when opened in 2.8x: ``` write_customdata error: layer '':15 - can't be written to file ``` Where '15' can be other numbers. Sometimes dozens of times whenever whatever is throwing this error updates, such as on a frame change, and blender is momentarily unresponsive. I've found that through process of elimination by deleting data, and I've tracked down a specific example of a mesh data block that triggers the error so you can repro. Deleting the object does not stop the error, but deleting the mesh data immediately does. I can't stress enough that this normally applies to dozens of objects in a complex file like a rigged character, so tracking down each one is a long process during which blender is extremely laggy. Repro steps: Open attatched .blend file, open console, and change the current frame. Since I've only kept one piece of mesh data that causes it, you should see the error once per frame change. Note: For some reason, switching into and out of edit mode also stops the error, but this isn't always practical in a complex file with hundreds or thousands of objects. [customdata error.blend](https://archive.blender.org/developer/F8444357/customdata_error.blend)

Stellarator Tokamak commented

2020-04-02 21:04:44 +02:00

Added subscriber: @AdrianPreston

Daniel Grauer commented

2020-04-03 11:23:13 +02:00

Added subscriber: @DanielGrauer

Richard Antalik commented

2020-04-09 15:03:39 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Bastien Montagne commented

2020-04-22 16:12:15 +02:00

Added subscriber: @mont29

Bastien Montagne self-assigned this 2020-04-22 16:12:15 +02:00

Bastien Montagne commented

2020-04-22 16:12:15 +02:00

Error message in itself is valid, issue here is that it is printed out on every undo step storage.

Note that switching to Edit mode, or saving/reloading once, will clear the stale invalid data, so you would not have those errors anymore.

Will silence the error when writing undo memfile.

Error message in itself is valid, issue here is that it is printed out on every undo step storage. Note that switching to Edit mode, or saving/reloading once, will clear the stale invalid data, so you would not have those errors anymore. Will silence the error when writing undo memfile.

blender-admin commented

2020-04-22 16:14:35 +02:00

This issue was referenced by 878cd0e124

This issue was referenced by 878cd0e1246f173066035e5240ed38016122bba4

Stellarator Tokamak commented

2020-04-22 17:00:27 +02:00

The other issue is that the message does not say which object(s) are causing the error, so identifying the offending object in a file with hundreds or thousands of objects is problematic.

Bastien Montagne commented

2020-04-22 17:13:13 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Bastien Montagne closed this issue

2020-04-22 17:13:13 +02:00

Thomas Dinges added this to the 2.83 LTS milestone 2023-02-08 16:38:06 +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

Error spam in console when opening file from 2.7x #75318