Change Details

**System Information** Operating system: windows 10 1903 Graphics card: GTX 1080ti **Blender Version** Broken: 2.83.1 stable (example: 2.79b release) (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen) Worked: (optional) **Short description of error** When editing object directly belongs to the scene collection, switch to object mode and press number keys to fast pick a collection. If the related collection is not checked, blender instantly crushes without any error message. It doesn't happen all the time, but quite often. I think maybe it has something to do with the editing did to the object. Sometimes I get a error message like this: {F8650751} In this project file, I changed the name of collection 1 to album. I tested opening another project file and press 1, blender still searches for the collection named album. Is it possible that the part of collection numbering and naming function doesn't automaticly link to the current project? **Exact steps for others to reproduce the error** {F8650738} Create an object and move it to scene collection. Uncheck all collections then edit the object, I think some duplicate and seperate operations will get more chance to crush blender. Finally switch back to object mode and press 1.

**System Information** Operating system: windows 10 1903 Graphics card: GTX 1080ti **Blender Version** Broken: 2.83.1 stable (example: 2.79b release) (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen) Worked: (optional) **Short description of error** When editing object directly belongs to the scene collection, switch to object mode and press number keys to fast pick a collection. If the related collection is not checked, blender instantly crushes without any error message. It doesn't happen all the time, but quite often. I think maybe it has something to do with the editing did to the object. Sometimes I get a error message like this: {F8650751} In this project file, I changed the name of collection 1 to “album". I tested opening another project file and press 1, blender still searches for the collection named "album". Is it possible that the part of collection numbering and naming function doesn't automaticly link to the current project? **Exact steps for others to reproduce the error** {F8650738} Create an object and move it to scene collection. Uncheck all collections then edit the object, I think some duplicate and seperate operations will get more chance to crush blender. Finally switch back to object mode and press 1.

**System Information** Operating system: windows 10 1903 Graphics card: GTX 1080ti **Blender Version** Broken: 2.83.1 stable (example: 2.79b release) (example: 2.80, edbf15d3c044, blender2.8, 2018-11-28, as found on the splash screen) Worked: (optional) **Short description of error** When editing object directly belongs to the scene collection, switch to object mode and press number keys to fast pick a collection. If the related collection is not checked, blender instantly crushes without any error message. It doesn't happen all the time, but quite often. I think maybe it has something to do with the editing did to the object. Sometimes I get a error message like this: {F8650751} In this project file, I changed the name of collection 1 to “album". I tested opening another project file and press 1, blender still searches for the collection named "album". Is it possible that the part of collection numbering and naming function doesn't automaticly link to the current project? **Exact steps for others to reproduce the error** {F8650738} Create an object and move it to scene collection. Uncheck all collections then edit the object, I think some duplicate and seperate operations will get more chance to crush blender. Finally switch back to object mode and press 1.