Page MenuHome

Make Single User crashes
Closed, ResolvedPublic


System Information
Operating system: Windows 10 Pro 64bit
Graphics card: GTX 960

Blender Version
2.80 Beta Hash 4c31bed6b46

Short description of error

When I select an object and access Object > Relations > Make Single User > Object and Data > Selected Objects, Blender crashes and closes.

Event Timeline

Jacques Lucke (JacquesLucke) triaged this task as Needs Information from User priority.

I don't know how to reproduce this exactly. Please provide an as-simple-as-possible .blend file and a screenshot that shows where I have to click to make it crash.

Blender closes after clicking "Selected Objects".

Philipp Oeser (lichtwerk) raised the priority of this task from Needs Information from User to Confirmed, Medium.

Confirmed, something wrong with the iterators data_in

1  object_bases_iterator_begin                    layer.c              1135 0x2b82a0b 
2  objects_iterator_begin                         layer.c              1182 0x2b82b9b 
3  BKE_view_layer_selected_objects_iterator_begin layer.c              1210 0x2b82c40 
4  single_obdata_users                            object_relations.c   1766 0x2152232 
5  make_single_user_exec                          object_relations.c   2459 0x21543d9

I guess this one is for @Dalai Felinto (dfelinto)?

Philipp Oeser (lichtwerk) raised the priority of this task from Confirmed, Medium to Confirmed, High.

Upping priority here (since it has been reported quite a few times now...)

@deflinto: mind checking?

This bug was introduced between the Win10 64 build dated 251118 ending 3d8 (where it was not present) and 271118 build ending 436 (where it was present).
Interestingly it was after the 25th of Nov build that a lot of us reported performance slowdowns using eeVee. For me it was scrolling through the time line was too slow to be usable so I am still using the pre271118 build for my work.

This was originally reported as T58188: Extreme FPS loss (24x) between 2.79 and 2.8 with particle systems where I think it may have been misdiagnosed.

Hope this helps