Page MenuHome

Blender 2.78 crashes after loading data from a blendfile
Closed, ResolvedPublic

Description

System Information
Windows 7 64bit, NVIDIA Quadro K3100M

Blender Version
Broken: 2.78a
Worked: 2.77a

Short description of error

Blender 2.78 crashes after loading data from a blendfile

Exact steps for others to reproduce the error

I'm importing data from another blendfile as follows:

def import_from_file(filepath):
    with bpy.data.libraries.load(filepath) as (data_from, data_to):
        collections = 'objects', 'groups', 'materials'
        for collection_name in collections:
            collection_from = getattr(data_from, collection_name)
            collection_to = getattr(data_to, collection_name)
            for obj in collection_from:
                collection_to.append(obj) 
        
    for obj in data_to.objects:
        bpy.context.scene.objects.link(obj)

The import works fine but afterwards some API operations crash Blender with Error: EXCEPTION_ACCESS_VIOLATION. For example bpy.ops.object.select_all(action='DESELECT').

This is working correctly in 2.77a.

Event Timeline

Bastien Montagne (mont29) lowered the priority of this task from 90 to 30.Oct 28 2016, 3:45 PM

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Attached two files. Running the main.py script of the main.blend file reproduces this issue.

Bastien Montagne (mont29) raised the priority of this task from 30 to 50.

Confirmed, think the issue here is that data_to.objects holds pointer references to linked data-blocks, but some of those data-blocks may have been copied (and then deleted) during the 'make local' process following linking, for append operation.

@Bastien Montagne (mont29) Is there an ETA for the next release including this fix?

No, nothing is decided yet, would not happen before two months at least I think…

Marc (schlamar) changed the task status from Resolved to Unknown Status.Feb 14 2017, 3:18 PM

This is not resolved in 2.78b!

My script to reproduce the issue (see my comment) is still crashing (Windows 7, 64bit).

The daily build (930186d) does work. Could it be that this fix didn't make it in the release? :(

Bastien Montagne (mont29) changed the task status from Unknown Status to Resolved.Feb 14 2017, 6:20 PM

2.78b is a 'performances' release, not a bugfix release. Please wait for 2.79 (and do not reopen reports like that, too!).