Crash switching to Modeling then Sculpting Workspace #58066

New Issue

Gavin Scott · 2018-11-26T18:09:23+01:00

Gavin Scott commented

2018-11-26 18:09:23 +01:00

System Information
Windows 10 Nvidia 1060

Blender Version
2.80 current commit.

Short description of error
Blender crashes when switching to Modeling then Sculpting Workspace.

Exact steps for others to reproduce the error

Open Blender, dismiss splash, click /Modeling\ workspace tab, click /Sculpting\ tab, crash:

Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF6DA6C2B5D
Module : G:\bdev\build_windows_Release_x64_vc15_Release\bin\release\blender.exe

**System Information** Windows 10 Nvidia 1060 **Blender Version** 2.80 current commit. **Short description of error** Blender crashes when switching to Modeling then Sculpting Workspace. **Exact steps for others to reproduce the error** Open Blender, dismiss splash, click /Modeling\ workspace tab, click /Sculpting\ tab, crash: Error : EXCEPTION_ACCESS_VIOLATION Address : 0x00007FF6DA6C2B5D Module : G:\bdev\build_windows_Release_x64_vc15_Release\bin\release\blender.exe

Gavin Scott commented

2018-11-26 18:09:23 +01:00

Added subscriber: @GavinScott

blender-admin commented

2018-11-26 18:09:23 +01:00

#58096 was marked as duplicate of this issue

blender-admin commented

2018-11-26 18:09:23 +01:00

#58087 was marked as duplicate of this issue

blender-admin commented

2018-11-26 18:09:23 +01:00

#58078 was marked as duplicate of this issue

ThinkingPolygons commented

2018-11-26 20:36:42 +01:00

Added subscriber: @ThinkingPolygons

ThinkingPolygons commented

2018-11-26 20:36:42 +01:00

Confirmed.

Daniel Salazar commented

2018-11-26 22:51:26 +01:00

Added subscriber: @zanqdo

Daniel Salazar commented

2018-11-26 22:51:26 +01:00

Double confirmed

Daniel Salazar commented

2018-11-26 22:53:56 +01:00

Have you guys thought about a getting into test driven development?

Gavin Scott commented

2018-11-27 07:34:41 +01:00

This crash seems to have been fixed by one of this evening's commits, but I'm not sure which one.

Can you guys confirm that it's not doing it for you either after building the latest (or get tonight's buildbot build)?

This crash seems to have been fixed by one of this evening's commits, but I'm not sure which one. Can you guys confirm that it's not doing it for you either after building the latest (or get tonight's buildbot build)?

Philipp Oeser commented

2018-11-27 15:00:46 +01:00

Added subscriber: @Jack-Pierrot

Philipp Oeser commented

2018-11-27 15:01:07 +01:00

Added subscriber: @AugustoCezar

Daniel Salazar commented

2018-11-27 16:58:40 +01:00

It's still crashing. If it doesn't crash at first try switching to a few tabs and then sculpt

Gavin Scott commented

2018-11-27 17:07:03 +01:00

It has always been at least a little non-deterministic like it's an uninitialized (and thus random) variable kind of thing.

Since commits from last night and still this morning I just can't get it to crash anymore here, but that may just be that the changes perturbed things just enough in my build environment that it's unable to happen or at least much less frequent.

The "if it doesn't crash at first then switch around tabs until it does" was the behavior here before as well.

It has always been at least a little non-deterministic like it's an uninitialized (and thus random) variable kind of thing. Since commits from last night and still this morning I just can't get it to crash anymore here, but that may just be that the changes perturbed things just enough in my build environment that it's unable to happen or at least much less frequent. The "if it doesn't crash at first then switch around tabs until it does" was the behavior here before as well.

Benjamin Humpherys commented

2018-11-27 17:22:54 +01:00

Added subscriber: @brhumphe

Benjamin Humpherys commented

2018-11-27 17:22:54 +01:00

Also confirmed on the latest build for Mac. UV Editing -> Sculpting also crashes.

Daniel Salazar commented

2018-11-27 18:14:13 +01:00

I think this is supposed to be fixed on 1d4ad68198 while the latest build is only 26b1aa9943 so it might indeed be fixed already but have to wait for next autobuild to confirm

I think this is supposed to be fixed on 1d4ad6819857 while the latest build is only 26b1aa99436 so it might indeed be fixed already but have to wait for next autobuild to confirm

Brecht Van Lommel commented

2018-11-27 18:59:58 +01:00

Added subscriber: @FrancescoArena