Page MenuHome

Data belonging to unused appended group is impossible to delete from file
Closed, ArchivedPublic


If a group is appended from another file, it is impossible to remove the group datablock, as well as the object/mesh/etc. datablocks because the original objects are not in the scene and can't be deleted. Even if the group datablock has no duplicator objects using it, and no objects in any scenes are members of it, it doesn't get purged like other 0-user datablocks in blender on file save. This also prevents all of the datablocks used by the group from being purged.

This bug was reported in 2006:

And was incorrectly closed due to being marked as archived. This behavior still exists.



Event Timeline

Diet Coke (dlots) added a project: BF Blender.
Diet Coke (dlots) set Type to Bug.
Diet Coke (dlots) created this task.
Diet Coke (dlots) raised the priority of this task from to Needs Triage by Developer.
Aaron Carlisle (Blendify) removed Ton Roosendaal (ton) as the assignee of this task.

Please don't make assignments yourself

What blender version are you using

This is also occuring with this plugin because the plugin does not place the objects assigned to the group into the scene anywhere (as opposed to append, which does).

This is an issue that stems from the fact that it is (presumably) impossible to remove an object from a group causing a recursive usage scenario. It appears to be not possible to remove an object from a group in the UI other than from the Properties panel when said object is selected. However, it's not possible to select a deleted object.

Essentially this appears to be an issue of an object not being removed from a group though it doesn't exist anywhere in the scenes.

To accomplish this orphaned scenario. Append an instance of a group (an empty duplicating a group). This will append the instance and the contents of the group. Delete the instance and the contents with one operation. Normally, this will remove the objects from the Datablocks view of the outliner, because they will not have a user, in this case this recursive orphaning occurs.

This is with 2.74 3-31 release from the main site and has been occuring since atleast 2.65, but presumably during all of Blender's life.

You can append the test duplicating empty from this provider file.

I have a file that has materials caused by workflow as well. I don't quite remember how these materials accumulated these ghost users but I will try to remember.

In addition, this plugin:

May be interacting with the algorithm that culls recursive orphaned objects as relevant to this error.

I think that I can delete it in the following procedures.

Carry out 'Link Group Objects To Scene' for each groups.

Because Objects becomes selectable, delete the Group setting of each Object.

Delete each Objects.
After having saved it, load it.
Carry out 'Unlink Group' for each group.
After having saved it, load it.
It should be deleted all.

This is the result that I deleted from group_paste_error_consumer.blend.

I think this can even be done quicker by selecting ´orphaned data' in the outliner and clicking 'Purge all' (but you need to do that twice)

The addon appends a bunch of materials and particle systems from a bundled library but does not instance any objects in the scene. So all those items are in fact immediately orphaned, unless the user selects one of them to use on a tree object.

Now any objects with zero users are purged on saving the .blend (just like when you click purge all) but this is not done recursively: the object for example are purge but leave their associated meshes with zero user in turn and these are not purged (unless you click Purge all again).

So the bug (if it is a bug, their might be a good reason for this behaviour) is that purge-on-save does not act recursively.

Brecht Van Lommel (brecht) closed this task as Archived.
Brecht Van Lommel (brecht) claimed this task.

This is currently the intended behavior for groups, they are not removed automatically even if they have zero users. It's one of the datablocks that have this exception. It might be good to remove at some point, but that gives various other issues which then need to be solved first, so it's not a simple change and more of a bigger redesign.

And yes, having to load and save multiple times to get rid of all unused datablocks is silly, but it's not considered a bug at the moment and is a limitation in the current design.

For anyone who has come across this issue in 2018:

In my case, a linked group of a shrub model was preventing the same model from then being appended, and it seemed nearly impossible to delete the offending group. Well, it is not impossible! :-)

In the Outliner, select "Blender File" for type of data to display, and inside "Groups", right-click on the offending group and press Delete. You may need to save, close, and re-open the .blend file. Then you will need to scroll down to the linked data section (identified by a Document Icon with an Arrow), right-click it, and select "Delete". Again, you may need to save, close, and re-open the .blend for the changes to take effect. Now you should be able to append the file as normal. :-)

I thank God for a much simpler solution to this issue. Posted answer on StackExchange here.