Severe problem with multiple instances of a library (save and reload) #53977

New Issue

Manuel Rais · 2018-02-01T15:31:32+01:00

Manuel Rais commented

2018-02-01 15:31:32 +01:00

System Information
Linux Mint 18 Sarah (Ubuntu 16.04.3 LTS)

Blender Version
Broken: 2.79 5bd8ac9abf

Short description of error
When renaming a library filepath to match another already linked, blender mixed libraries.
Example : lib_v01.blend, other_lib.blend and lib_v02.blend are linked in a blendfile (the link order is important).
When I rename lib_v01.blend to lib_v02.blend, save and reopen, Blender "merge" the multiple instances of lib_v02.blend.
But one of the Suzanne is now "attached" to other_lib.blend (instead of lib_v02.blend), and obvioulsy Blender doesn't find it.

Exact steps for others to reproduce the error

Create a new blender file.
Link the "Suzanne" group from lib_v01.blend
Link the "Sphere" group from other_lib.blend
Link the "Suzanne" group from lib_v02.blend
Save the file.
In the outliner, rename lib_v01.blend to lib_v02.blend
Save and reopen the blendfile

lib_v02.blend

lib_v01.blend

other_lib.blend

**System Information** Linux Mint 18 Sarah (Ubuntu 16.04.3 LTS) **Blender Version** Broken: 2.79 5bd8ac9abfa **Short description of error** When renaming a library filepath to match another already linked, blender mixed libraries. Example : lib_v01.blend, other_lib.blend and lib_v02.blend are linked in a blendfile (the link order is important). When I rename lib_v01.blend to lib_v02.blend, save and reopen, Blender "merge" the multiple instances of lib_v02.blend. But one of the Suzanne is now "attached" to other_lib.blend (instead of lib_v02.blend), and obvioulsy Blender doesn't find it. **Exact steps for others to reproduce the error** 1. Create a new blender file. 2. Link the "Suzanne" group from lib_v01.blend 3. Link the "Sphere" group from other_lib.blend 4. Link the "Suzanne" group from lib_v02.blend 5. Save the file. 6. In the outliner, rename lib_v01.blend to lib_v02.blend 7. Save and reopen the blendfile [lib_v02.blend](https://archive.blender.org/developer/F2075484/lib_v02.blend) [lib_v01.blend](https://archive.blender.org/developer/F2075483/lib_v01.blend) [other_lib.blend](https://archive.blender.org/developer/F2075503/other_lib.blend)

Manuel Rais commented

2018-02-01 15:31:32 +01:00

Added subscriber: @g-lul

ronan ducluzeau commented

2018-02-01 18:04:01 +01:00

Added subscriber: @zeauro

ronan ducluzeau commented

2018-02-01 18:04:01 +01:00

Sorry. But I don't understand what behaviour you are expecting.

You linked one suzanne from lib_v01, one suzanne from lib_v02 and one sphere from other_lib.

You renamed lib_v01 and only lib_v01. You did not rename other_lib. You did not do anything to sphere.
So when .blend is saved and reloaded, why do you expect link to other_lib to be removed ? Sphere is still attached to it.

Blender does not go further away than changes made by user.

Sorry. But I don't understand what behaviour you are expecting. You linked one suzanne from lib_v01, one suzanne from lib_v02 and one sphere from other_lib. You renamed lib_v01 and only lib_v01. You did not rename other_lib. You did not do anything to sphere. So when .blend is saved and reloaded, why do you expect link to other_lib to be removed ? Sphere is still attached to it. Blender does not go further away than changes made by user.

Manuel Rais commented

2018-02-01 19:22:53 +01:00

Hi,
I'm not expecting other_lib.blend to be removed but the second Suzanne (from lib_v01.blend) to be linked to lib_v02.blend. And this is not happening. After save reopen, for blender, the second Suzanne is linked to other_lib.blend (but Suzanne has never be part of it).
Did you try the steps to reproduce this bug ?

Hi, I'm not expecting other_lib.blend to be removed but the second Suzanne (from lib_v01.blend) to be linked to lib_v02.blend. And this is not happening. After save reopen, for blender, the second Suzanne is linked to other_lib.blend (but Suzanne has never be part of it). Did you try the steps to reproduce this bug ?

ronan ducluzeau commented

2018-02-01 23:32:28 +01:00

Sorry. I did not follow correct order.

So, instances are removed on name basis but links are remapped according to their creation order.

Sorry. I did not follow correct order. So, instances are removed on name basis but links are remapped according to their creation order.

Manuel Rais commented

2018-02-02 18:12:42 +01:00

Hi,
The issue is here since blender 2.76a I think.
2.75a does not have it.

Hi, The issue is here since blender 2.76a I think. 2.75a does not have it.

Bastien Montagne commented

2018-02-13 13:51:53 +01:00

Added subscriber: @mont29

Bastien Montagne self-assigned this 2018-02-13 13:51:53 +01:00

Bastien Montagne commented

2018-02-13 13:51:53 +01:00

Well, at least library relocation (rightclick on a lib in outliner, Relocate) does work correctly it seems.

Will see whether we can fix the issue with mere lib renaming, but I doubt this was ever supported, setting same paths for two different lib objects is really, really pulling Blender to its limits…

Well, at least library relocation (rightclick on a lib in outliner, Relocate) does work correctly it seems. Will see whether we can fix the issue with mere lib renaming, but I doubt this was ever supported, setting same paths for two different lib objects is really, really pulling Blender to its limits…

Manuel Rais commented

2018-02-13 14:54:23 +01:00

Ok Bastien,
Thanks :)

Ok Bastien, Thanks :)

Manuel Rais commented

2018-02-13 15:01:42 +01:00

Can I call the relocate operator from a python file ? I can't see any parameters with it. Or maybe bpy.ops.wm.lib_relocate can do the job ?

Bastien Montagne commented

2018-02-13 17:53:04 +01:00

In #53977#484387, @g-lul wrote:
Can I call the relocate operator from a python file ? I can't see any parameters with it. Or maybe bpy.ops.wm.lib_relocate can do the job ?

Yes, outside of outliner you should use bpy.ops.wm.lib_relocate directly (outliner version is a mere wrapper around that one anyway).

> In #53977#484387, @g-lul wrote: > Can I call the relocate operator from a python file ? I can't see any parameters with it. Or maybe bpy.ops.wm.lib_relocate can do the job ? Yes, outside of outliner you should use `bpy.ops.wm.lib_relocate` directly (outliner version is a mere wrapper around that one anyway).

Bastien Montagne commented

2018-02-13 21:14:51 +01:00

Added subscriber: @Sergey

Bastien Montagne commented

2018-02-13 21:14:51 +01:00

Ok found the core of the issue.

@Sergey I would not be surprised if this was also the cause of the mysterious problems with disappearing libs at the studio.

Have a partial fix, but now we get multiple copies of same linked datablock (like, two copies of Suzanne group from lib_v02 in this report's demo), which is not a good thing either. Still investigating how to fix that second half of the issue…

Ok found the core of the issue. @Sergey I would not be surprised if this was also the cause of the mysterious problems with disappearing libs at the studio. Have a partial fix, but now we get multiple copies of same linked datablock (like, two copies of Suzanne group from lib_v02 in this report's demo), which is not a good thing either. Still investigating how to fix that second half of the issue…

Manuel Rais commented

2018-02-15 14:31:46 +01:00

Hi,
I've tried to use the bpy.ops.wm.lib_relocate but I've got an issue with proxy relinking (I know you're in love with proxies Bastien :) ).
I've also tried with the bpy.ops.outliner.relocate in the outliner through the interface and the same error appears.
Result : the armature proxy become an empty.

Pose copy error, pose to:0x7f07ec228c28 from:(nil)
Proxy copy error, lib Object: Armature proxy Object: cube_proxy
Error: Not freed memory blocks: 1, total unfreed memory 0.001144 M

Is this a known bug ? If not, I'll try to do a bug report. I have a simple case to reproduce it.

Hi, I've tried to use the `bpy.ops.wm.lib_relocate` but I've got an issue with proxy relinking (I know you're in love with proxies Bastien :) ). I've also tried with the `bpy.ops.outliner.relocate` in the outliner through the interface and the same error appears. Result : the armature proxy become an empty. ``` Pose copy error, pose to:0x7f07ec228c28 from:(nil) Proxy copy error, lib Object: Armature proxy Object: cube_proxy Error: Not freed memory blocks: 1, total unfreed memory 0.001144 M ``` Is this a known bug ? If not, I'll try to do a bug report. I have a simple case to reproduce it.

Bastien Montagne commented

2018-02-15 15:54:54 +01:00

Yep, would appreciate a report about this, relocate should work (but indeed most likely not all corner cases with ugly proxies are ironed out yet :( ).

Yep, would appreciate a report about this, relocate *should* work (but indeed most likely not all corner cases with ugly proxies are ironed out yet :( ).

Manuel Rais commented

2018-02-16 09:45:55 +01:00

@mont29 Apparently, the "relocate bug" is not in the 2.79 release but in the 2.78a.
Should I report it nonetheless ?

@mont29 Apparently, the "relocate bug" is not in the 2.79 release but in the 2.78a. Should I report it nonetheless ?

Bastien Montagne commented

2018-02-16 10:37:01 +01:00

@g-lul Nope, in fact if a bug does not affect current master, there’s no point in reporting it, since it has already (presumably) been solved. :)

Bastien Montagne commented

2018-02-16 10:46:18 +01:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2018-02-16 10:46:18 +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

Severe problem with multiple instances of a library (save and reload) #53977