Baking Selected to Active crashes blender when in edit mode. #59360

New Issue

Joanna Vetulani · 2018-12-14T11:48:28+01:00

Joanna Vetulani commented

2018-12-14 11:48:28 +01:00

System Information
Operating system: Ubuntu 18.04
Graphics card: GTX 1080

Blender Version
Broken: 2.80 aca13040da
Worked: 2.79b

This used to a be a thing done to see polygon lines in the UV image editor and track the progress of the bake with the uv lines overlay - Cycles doesn't show the progress per triangle, but baking is still allowed in edit mode and leads to a crash - probably due to the multiediting change?

System Information Operating system: Ubuntu 18.04 Graphics card: GTX 1080 Blender Version Broken: 2.80 aca13040dac Worked: 2.79b This used to a be a thing done to see polygon lines in the UV image editor and track the progress of the bake with the uv lines overlay - Cycles doesn't show the progress per triangle, but baking is still allowed in edit mode and leads to a crash - probably due to the multiediting change?

Joanna Vetulani commented

2018-12-14 11:48:29 +01:00

Added subscriber: @Jasiek

Jacques Lucke commented

2018-12-14 11:52:19 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2018-12-14 11:52:19 +01:00

Could you prepare a simple .blend file that helps us to reproduce the issue, please?

Joanna Vetulani commented

2018-12-14 15:17:26 +01:00

Sure!
BakeBoxSurfaceWeightedNormals.blend

Select the high poly, select the low poly, go into edit mode and hit bake - Blender crashes instantly.

Sure! [BakeBoxSurfaceWeightedNormals.blend](https://archive.blender.org/developer/F5952792/BakeBoxSurfaceWeightedNormals.blend) Select the high poly, select the low poly, go into edit mode and hit bake - Blender crashes instantly.

Jacques Lucke commented

2018-12-14 15:40:29 +01:00

Hm, I can't reproduce it, maybe I'm doing something wrong. Is it possible for you to change the .blend file so that you only have to press Bake to make it crash?

Hm, I can't reproduce it, maybe I'm doing something wrong. Is it possible for you to change the .blend file so that you *only* have to press Bake to make it crash?

Joanna Vetulani commented

2018-12-14 15:52:02 +01:00

BakeBox_EditModeCrash.blend

Hit TAB twice and then bake and it'll crash - if you just open it when it was saved with both objects selected and in edit mode it will bake out ok and not crash, if you do TAB and TAB again to go out of edit mode into object mode, and into edit mode again and hit bake, it'll crash

I've also recorded a video:
https://www.youtube.com/watch?v=ua4KNyf9ziI

I've been getting the same behaviour since 2,8 first came out - is there some bug log I can send you to help if you can't reproduce it?

[BakeBox_EditModeCrash.blend](https://archive.blender.org/developer/F5952977/BakeBox_EditModeCrash.blend) Hit TAB twice and then bake and it'll crash - if you just open it when it was saved with both objects selected and in edit mode it will bake out ok and not crash, if you do TAB and TAB again to go out of edit mode into object mode, and into edit mode again and hit bake, it'll crash I've also recorded a video: https://www.youtube.com/watch?v=ua4KNyf9ziI I've been getting the same behaviour since 2,8 first came out - is there some bug log I can send you to help if you can't reproduce it?

Jacques Lucke commented

2018-12-14 16:04:13 +01:00

ok, I'm doing exactly the same thing you are doing in the video, even in the exact same version and still can't reproduce it.

Waiting for someone else to try it now.

ok, I'm doing exactly the same thing you are doing in the video, even in the exact same version and still can't reproduce it. Waiting for someone else to try it now.

Joanna Vetulani commented

2018-12-14 16:24:28 +01:00

Are you also testing this on Linux?

Running Ubuntu 18.04 with Kernel 4.16.10-041610-generic
Nvidia driver version 396.54

The CPU is an Intel i7-8700K

If it's nothing OS or Hardware specific maybe it's some old setting that's being carried over for me from a previous version?

Here's a crash log:
BakeBoxSurfaceWeightedNormals.crash.txt
And terminal output when I run Blender, leading up to the crash:
BlenderTerminalOutput.txt

Are you also testing this on Linux? Running Ubuntu 18.04 with Kernel 4.16.10-041610-generic Nvidia driver version 396.54 The CPU is an Intel i7-8700K If it's nothing OS or Hardware specific maybe it's some old setting that's being carried over for me from a previous version? Here's a crash log: [BakeBoxSurfaceWeightedNormals.crash.txt](https://archive.blender.org/developer/F5953213/BakeBoxSurfaceWeightedNormals.crash.txt) And terminal output when I run Blender, leading up to the crash: [BlenderTerminalOutput.txt](https://archive.blender.org/developer/F5953222/BlenderTerminalOutput.txt)

Sebastian Parborg commented

2018-12-14 16:53:40 +01:00

Added subscribers: @brecht, @ZedDB

Brecht Van Lommel was assigned by Sebastian Parborg

2018-12-14 16:53:40 +01:00

Sebastian Parborg commented

2018-12-14 16:53:40 +01:00

I can reproduce this on f85b05111f

I get asserts in my debug build:

blender: /home/zed/programmering/blender_master/blender/intern/cycles/kernel/../kernel/kernel_compat_cpu.h:77: const T& ccl::texture<T>::fetch(int) [with T = ccl::uint4]: Assertion `index >= 0 && index < width' failed.

Backtrace from non debug build:

Thread 45 "blender" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffb63ff700 (LWP 12359)]
0x0000555556f83fc2 in ccl::kernel_bake_evaluate(ccl::KernelGlobals*, ccl::uint4*, ccl::float4*, ccl::ShaderEvalType, int, int, int, int) ()
(gdb) bt
- 0  0x0000555556f83fc2 in ccl::kernel_bake_evaluate(ccl::KernelGlobals*, ccl::uint4*, ccl::float4*, ccl::ShaderEvalType, int, int, int, int) ()
- 1  0x0000555556d72127 in ccl::CPUDevice::thread_shader(ccl::DeviceTask&) ()
- 2  0x00005555570ee563 in ccl::TaskScheduler::thread_run(int) ()
- 3  0x00005555570efbce in ccl::thread::run(void*) ()
#4  0x00007ffff2ef629e in std::execute_native_thread_routine (__p=0x7fffcc84e360)
    at /var/tmp/portage/sys-devel/gcc-8.2.0-r5/work/gcc-8.2.0/libstdc++-v3/src/c++11/thread.cc:80
- 5  0x00007ffff5d9b3c3 in start_thread () from /lib64/libpthread.so.0
- 6  0x00007ffff329936f in clone () from /lib64/libc.so.6

@brecht should I assign cycles issues to someone else than you?

I can reproduce this on f85b05111fa4b96228a4a3969945c80fbb67f499 I get asserts in my debug build: ``` blender: /home/zed/programmering/blender_master/blender/intern/cycles/kernel/../kernel/kernel_compat_cpu.h:77: const T& ccl::texture<T>::fetch(int) [with T = ccl::uint4]: Assertion `index >= 0 && index < width' failed. ``` Backtrace from non debug build: ``` Thread 45 "blender" received signal SIGSEGV, Segmentation fault. [Switching to Thread 0x7fffb63ff700 (LWP 12359)] 0x0000555556f83fc2 in ccl::kernel_bake_evaluate(ccl::KernelGlobals*, ccl::uint4*, ccl::float4*, ccl::ShaderEvalType, int, int, int, int) () (gdb) bt - 0 0x0000555556f83fc2 in ccl::kernel_bake_evaluate(ccl::KernelGlobals*, ccl::uint4*, ccl::float4*, ccl::ShaderEvalType, int, int, int, int) () - 1 0x0000555556d72127 in ccl::CPUDevice::thread_shader(ccl::DeviceTask&) () - 2 0x00005555570ee563 in ccl::TaskScheduler::thread_run(int) () - 3 0x00005555570efbce in ccl::thread::run(void*) () #4 0x00007ffff2ef629e in std::execute_native_thread_routine (__p=0x7fffcc84e360) at /var/tmp/portage/sys-devel/gcc-8.2.0-r5/work/gcc-8.2.0/libstdc++-v3/src/c++11/thread.cc:80 - 5 0x00007ffff5d9b3c3 in start_thread () from /lib64/libpthread.so.0 - 6 0x00007ffff329936f in clone () from /lib64/libc.so.6 ``` @brecht should I assign cycles issues to someone else than you?

Brecht Van Lommel removed their assignment 2018-12-14 16:55:49 +01:00

Dalai Felinto was assigned by Brecht Van Lommel

2018-12-14 16:55:49 +01:00

Brecht Van Lommel commented

2018-12-14 16:55:49 +01:00

Added subscriber: @dfelinto

Brecht Van Lommel commented

2018-12-14 16:55:49 +01:00

@dfelinto was working on baking recently.

Dalai Felinto removed their assignment 2018-12-14 21:58:00 +01:00

Sergey Sharybin was assigned by Dalai Felinto

2018-12-14 21:58:00 +01:00

Dalai Felinto commented

2018-12-14 21:58:00 +01:00

Added subscriber: @Sergey

Dalai Felinto commented

2018-12-14 21:58:01 +01:00

Hey @Sergey I only get a crash if I build with WITH_OPENSUBDIV.
And the fact that it only happens if we toggle in/out of editmode raises a few flags that the issue is not on baking necessarily.

Hey @Sergey I only get a crash if I build with `WITH_OPENSUBDIV`. And the fact that it only happens if we toggle in/out of editmode raises a few flags that the issue is not on baking necessarily.

Dalai Felinto commented

2018-12-14 21:58:31 +01:00

Added subscriber: @ideasman42

Dalai Felinto commented

2018-12-14 21:58:31 +01:00

(and @ideasman42 - unrelated to the crash, but related to how the user is using edit mesh - this is another interesting use-case for having an option to disable multi-object editing, otherwise the HP and LP objects would necessarily be in edit mode, and both their UVs would show in the editor)

Brecht Van Lommel commented

2019-05-23 02:46:12 +02:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-05-23 02:46:12 +02:00

Brecht Van Lommel commented

2019-05-23 02:46:12 +02:00

This was fixed in e4c78436c6.

This was fixed in e4c78436c6.

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

Baking Selected to Active crashes blender when in edit mode. #59360