Page MenuHome

2.81 Cant open/append/link a blend file but 2.8 can
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15

Blender Version
Broken: version: 2.81 (sub 8), branch: master, commit date: 2019-09-08 21:40, hash: rBf3a4f12ac090
Worked: 2.8
Short description of error
same as title ...cmd prompt
shows
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF720FF2EF5
Module : C:\blender2.81\blender.exe

while trying to open

Copy pasting from 2.8 to 2.81 also crashes blender

re-importing the obj in a new 2.81 file works fine...
but don't know the this blend file is giving this issue

The file
just a chair model imported from an obj

Event Timeline

vprime (v_prime) updated the task description. (Show Details)

I have the same problem with the todays build!
I can´t open files I created with a blender version from last week friday. Blender 2.8 can open these files.

Philipp Oeser (lichtwerk) triaged this task as Confirmed, High priority.

Can confirm, checking... seems another problem with the new mapping node, crashes in versioning code...

1  update_mapping_node_inputs_and_properties versioning_cycles.c 802  0x2b535f5 
2  do_versions_after_linking_cycles          versioning_cycles.c 1096 0x2b54b73 
3  do_versions_after_linking                 readfile.c          9493 0x2b246ab 
4  blo_read_file_internal                    readfile.c          9799 0x2b2549d 
5  BLO_read_from_file                        readblenentry.c     320  0x2b5dfed 
6  BKE_blendfile_read                        blendfile.c         420  0x3e22900 
7  WM_file_read                              wm_files.c          631  0x3168daa 
8  wm_file_read_opwrap                       wm_files.c          2097 0x316c014 
9  wm_open_mainfile__open                    wm_files.c          2238 0x316c555 
10 wm_open_mainfile_exec                     wm_files.c          2273 0x316c621 
11 wm_handler_fileselect_do                  wm_event_system.c   2440 0x3160f90 
12 wm_handler_fileselect_call                wm_event_system.c   2538 0x316138d 
13 wm_handlers_do_intern                     wm_event_system.c   2926 0x3162753 
14 wm_handlers_do                            wm_event_system.c   2978 0x31628d3 
15 wm_event_do_handlers                      wm_event_system.c   3356 0x3163aa3 
16 WM_main                                   wm.c                417  0x31570cd 
17 main                                      creator.c           491  0x2b061c6

@Marcus Papathoma (machieb) You saved the file with last friday's build and Blender crashes when you open it with today's build?

@Omar Ahmad (OmarSquircleArt) I saved my files with version blender-2.81-4c4a8bf588c5-windows64 I downloaded last friday. I think it is a buildbot version from thursday night. With the todays build I can´t open these files.

@Omar Ahmad (OmarSquircleArt) : I tested a little bit and I can open my blend-file with blender-2.81-da25aca2677e-windows64. So the code that generates the error was integrated into blender after that version.

Looks like the file from the report was saved in (2, 80, 75), if I save it again today, we are on (2, 81, 8)

So I guess what happens is:

  • make a file (2, 81, 8) with mapping node OR open an older file with a mapping node in (2, 81, 8), save [TexMapping struct is gone]
  • open that file in something like (2, 80, 75), save again
  • open that one in (2, 81, 8) --> crash

@Philipp Oeser (lichtwerk) I see. Do we maintain forward compatibility in Blender?

I think usually TexMapping would be tagged DNA_DEPRECATED?
In this case I can still see it being used/added in node_composit_init_map_value / BKE_texture_mapping_add (for the composit MapValue node) though...

For the new Mapping Node, this clearly gets marked in red (Undefined) if opened in an older version, I guess this is fine in a way, but not sure how to handle these properly tbh, needs some futher digging...

We generally preserve some level of forward compatibility, but if you open the new mapping node in 2.80 it will definitely lead to data loss.

The same is true for many other features and we accept that. But a crash like this we can fix.