Maniphest T96486

One time purge when reopening scene, but complete when closing Blender
Closed, Archived

Assigned To
None
Authored By
Adrian (LalaGhost)
Mar 15 2022, 8:50 AM
Tags
  • BF Blender
Subscribers
Adrian (LalaGhost)
Richard Antalik (ISS)

Description

System Information
Operating system: Windows-10-10.0.19042-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3070 Laptop GPU/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 497.29

Blender Version
Broken: version: 3.1.0, branch: master, commit date: 2022-03-08 18:16, hash: rBc77597cd0e15

Short description of error
When you have a scene with unused data, aka Orphan Data, save the scene and reopening it without closing Blender, the Orphan Data will be handles as if you would press once on the purge button.
If you would close Blender completely, the Orphan Data will be deleted completely. Seems a bit strange to me that it is handled differently.

Exact steps for others to reproduce the error

  1. Create a cube, a new material with a texture assigned
  2. Duplicate the cube and press on the 2 next to the material and texture name to make it its own copy with a .001 in the name
  3. Delete the cube and go the Orphan Data in the View Layer
  4. Save the scene, open a new one and reopen the saved scene and you will see that the Orphan Data is gone as if you would have pressed the purge button once

Event Timeline

Adrian (LalaGhost) created this task.Mar 15 2022, 8:50 AM
Richard Antalik (ISS) changed the task status from Needs Triage to Needs Information from User.Mar 16 2022, 12:44 AM
Richard Antalik (ISS) added a subscriber: Richard Antalik (ISS).

If you would close Blender completely, the Orphan Data will be deleted completely. Seems a bit strange to me that it is handled differently.

I can't reproduce this. Also material with image texture will be still hanging there in orphan data for some reason.

The steps to reproduce are describing expected behavior. Can you provide steps for unexpected behavior, which is that all orphan data will be gone? Perhaps what I say is unexpected is expected by you, but I think this is how it's defined in code, but will have to check that to be absolutely sure.

Adrian (LalaGhost) added a comment.Mar 16 2022, 9:11 AM

Actually I could not reproduce the purge of all data
But it deletes the mesh data after opening, is this expected?

Richard Antalik (ISS) closed this task as Archived.Mar 16 2022, 11:40 PM
In T96486#1323881, @Adrian (LalaGhost) wrote:

Actually I could not reproduce the purge of all data
But it deletes the mesh data after opening, is this expected?

Yes, that is expected. Mesh is listed as data not used by any other data. Reason why "sub data" are not removed is because they are used by mesh. So this check is not recursive.

Will close since this is working as expected.