Crash on undo (possible due broken workspace) #69519

New Issue

Cirno · 2019-09-05T05:48:15+02:00

Cirno commented

2019-09-05 05:48:15 +02:00

System Information
Operating system: Windows-8.1-6.3.9600 64 Bits
Graphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.71

Blender Version
Broken: version: 2.81 (sub 8), branch: master, commit date: 2019-09-04 21:17, hash: baaa89a0bc

Short description of error
Blender crash every time I use undo in object mode on this scene. Crashes are most likely caused by broken workspace (even if this workspace isn't active)

Exact steps for others to reproduce the error

Open file (with "Load UI" checked)
Select any object.
Move, scale, rotate or add modifier
Press undo (ctrl+z) and blender will crash

Debug log says
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF74B732B18

After deleting "Quads" workspace it will no longer crash on undo.
Push Arm.blend

**System Information** Operating system: Windows-8.1-6.3.9600 64 Bits Graphics card: GeForce GT 730/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.71 **Blender Version** Broken: version: 2.81 (sub 8), branch: master, commit date: 2019-09-04 21:17, hash: `baaa89a0bc` **Short description of error** Blender crash every time I use undo in object mode on this scene. Crashes are most likely caused by broken workspace (even if this workspace isn't active) **Exact steps for others to reproduce the error** 1. Open file (with "Load UI" checked) 2. Select any object. 3. Move, scale, rotate or add modifier 4. Press undo (ctrl+z) and blender will crash Debug log says Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF74B732B18 After deleting "Quads" workspace it will no longer crash on undo. [Push Arm.blend](https://archive.blender.org/developer/F7717790/Push_Arm.blend)

Cirno commented

2019-09-05 05:48:15 +02:00

Added subscriber: @Lambdadelta

Cirno changed title from ~~Crash on undo (2.81)~~ to Crash on undo (possible due broken workspace)

2019-09-05 06:57:55 +02:00

Dalai Felinto commented

2019-09-19 00:25:53 +02:00

Added subscriber: @dfelinto

Dalai Felinto commented

2019-09-19 00:25:53 +02:00

Thanks for the report. I can confirm this but I need some more information from you.

When was this file created? (which Blender version you used originally for it, approximately).
Can you reproduce it from scratch from a the latest 2.80 (blender.org/download) or a recent night build? (builder.blender.org)?

Crash:

0x00005555560e505f in lib_link_workspace_layout_restore (id_map=0x7fffd22ef808, newmain=0x7fffdb7d4808, layout=0x7fffdb6b1d48)

at //source/blender/blenloader/intern/readfile.c:7922

7922        for (ScrArea *sa = screen->areabase.first; sa; sa = sa->next) {

Full backtrace: P1106

Thanks for the report. I can confirm this but I need some more information from you. 1) When was this file created? (which Blender version you used originally for it, approximately). 2) Can you reproduce it from scratch from a the latest 2.80 (blender.org/download) or a recent night build? (builder.blender.org)? **Crash:** ```Thread 1 "blender" received signal SIGSEGV, Segmentation fault. 0x00005555560e505f in lib_link_workspace_layout_restore (id_map=0x7fffd22ef808, newmain=0x7fffdb7d4808, layout=0x7fffdb6b1d48) ``` at //source/blender/blenloader/intern/readfile.c:7922 ``` 7922 for (ScrArea *sa = screen->areabase.first; sa; sa = sa->next) { ``` **Full backtrace:** P1106

Cirno commented

2019-09-24 21:30:02 +02:00

File was created in some of the 2.81 beta versions. I worked on the scene for a couple days, then for some reason it began to crash on undo. There were more mesh objects and many cameras with backgrounds, I deleted them as they don't have any impact on crashes

I'm sorry, I don't know how to reproduce that buggy scene from scratch.

File was created in some of the 2.81 beta versions. I worked on the scene for a couple days, then for some reason it began to crash on undo. There were more mesh objects and many cameras with backgrounds, I deleted them as they don't have any impact on crashes I'm sorry, I don't know how to reproduce that buggy scene from scratch.

Bastien Montagne commented

2019-10-01 20:43:39 +02:00

Added subscriber: @mont29

Bastien Montagne commented

2019-10-01 20:43:39 +02:00

Changed status from 'Open' to: 'Archived'

Bastien Montagne closed this issue

2019-10-01 20:43:39 +02:00

Bastien Montagne self-assigned this 2019-10-01 20:43:39 +02:00

Bastien Montagne commented

2019-10-01 20:43:39 +02:00

Could have been during the fuzzy filebrowser changes era e.g., there were some issues with screens/workspaces at some points iirc. Or any other similar case. That happens during development, that’s why we keep producing 'stable' versions in addition to our daily builds of master. ;)

Cirno commented

2019-12-04 16:10:07 +01:00

This bug already happened to me twice on stable 2.81. It's the same - I move the object (or perform another operation in the object mode), press undo and blender will crash. File was created on 2.81 stable.

In this file crashes are due to default "Modeling" workspace. If I delete this workspace in the file, crashes will stop. And previous time (on stable 2.81 too) I got crashes because something happened in "UV Editing" workspace
UndoCrash.blend

This bug already happened to me twice on stable 2.81. It's the same - I move the object (or perform another operation in the object mode), press undo and blender will crash. File was created on 2.81 stable. In this file crashes are due to default "Modeling" workspace. If I delete this workspace in the file, crashes will stop. And previous time (on stable 2.81 too) I got crashes because something happened in "UV Editing" workspace [UndoCrash.blend](https://archive.blender.org/developer/F8189462/UndoCrash.blend)

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

Crash on undo (possible due broken workspace) #69519