Cycles Crash - Cycles crashes before sampling when certain meshes have autosmooth enabled. #50876

New Issue

Carlo Andreacchio · 2017-03-06T22:23:53+01:00

Carlo Andreacchio commented

2017-03-06 22:23:53 +01:00

System Information
Windows 7, core i7 920 x64 gtx1080

Blender Version
Broken: 80444ef (first crash on our builds was from 5c3216e)
Worked: 5552e83

Short description of error
On certain meshes with autosmooth enabled, cycles crashes out.

Exact steps for others to reproduce the error

Open attached blend file
press f12
crash
open attached blend file again
open mesh data tab
turn off autosmooth
press f12
no crash

It does not matter whether CPU or GPU rendering is enabled.

crash.blend

**System Information** Windows 7, core i7 920 x64 gtx1080 **Blender Version** Broken: 80444ef (first crash on our builds was from 5c3216e) Worked: 5552e83 **Short description of error** On certain meshes with autosmooth enabled, cycles crashes out. **Exact steps for others to reproduce the error** 1. Open attached blend file 2. press f12 3. crash 4. open attached blend file again 5. open mesh data tab 6. turn off autosmooth 7. press f12 8. no crash It does not matter whether CPU or GPU rendering is enabled. [crash.blend](https://archive.blender.org/developer/F504356/crash.blend)

Carlo Andreacchio commented

2017-03-06 22:23:53 +01:00

Changed status to: 'Open'

Carlo Andreacchio commented

2017-03-06 22:23:53 +01:00

Added subscriber: @candreacchio

Carlo Andreacchio commented

2017-03-07 00:26:19 +01:00

Potentially could be caused by 36c4fc1

Potentially could be caused by 36c4fc1

Sergey Sharybin commented

2017-03-07 10:05:19 +01:00

Added subscribers: @mont29, @Sergey

Bastien Montagne was assigned by Sergey Sharybin

2017-03-07 10:05:19 +01:00

Sergey Sharybin commented

2017-03-07 10:05:19 +01:00

Can confirm the crash, but not really familiar with the re-worked code from @mont29.

@mont29, mind having a look? The input mesh is valid, but for some reason *lnor_space is NULL. So either it's a bug somewhere deeper in lnot space calculation or we are missing some NULL pointer checks?

Can confirm the crash, but not really familiar with the re-worked code from @mont29. @mont29, mind having a look? The input mesh is valid, but for some reason `*lnor_space` is NULL. So either it's a bug somewhere deeper in lnot space calculation or we are missing some NULL pointer checks?

Bastien Montagne commented

2017-03-07 14:17:07 +01:00

Issue is deep in loop normals code actually, not specific to split faces. It's due to weird geometry, simplified the case in file below in case you'd like to add it as test @Sergey?

crash.blend

Still looking into a proper fix… :/

Issue is deep in loop normals code actually, not specific to split faces. It's due to weird geometry, simplified the case in file below in case you'd like to add it as test @Sergey? [crash.blend](https://archive.blender.org/developer/F504844/crash.blend) Still looking into a proper fix… :/

Sergey Sharybin commented

2017-03-07 15:01:28 +01:00

@mont29, nice simplification. I'll add it to the unit tests once the issue is solved, so we don't move tests/code into inconsistent state.

Carlo Andreacchio commented

2017-03-13 01:11:16 +01:00

We have figured out how we are creating these meshes (combination of remove doubles -> limited dissolve with autosmooth shade enabled, our usual process for cleaning up high poly objects which don't need to have that much complexity to them)

Just wondering if there has been any update to this bug?

We have figured out how we are creating these meshes (combination of remove doubles -> limited dissolve with autosmooth shade enabled, our usual process for cleaning up high poly objects which don't need to have that much complexity to them) Just wondering if there has been any update to this bug?

Bastien Montagne commented

2017-03-13 07:55:51 +01:00

Yes there, I understand the problem and have a first version of fix, but not much happy with it currently, trying to find a better solution.

Note that it’s actually a bug deep in custom normals process, which can also (among other thing) generate wrong normals at those vertices…

Yes there, I understand the problem and have a first version of fix, but not much happy with it currently, trying to find a better solution. Note that it’s actually a bug deep in custom normals process, which can also (among other thing) generate wrong normals at those vertices…

blender-admin commented

2017-03-13 16:13:47 +01:00

This issue was referenced by 1410ea0478

This issue was referenced by 1410ea04788aad95f84b5d8caf077f9d8b51d0c3

Bastien Montagne commented

2017-03-14 14:13:57 +01:00

Changed status from 'Open' to: 'Resolved'

Bastien Montagne closed this issue

2017-03-14 14:13:57 +01:00

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

Cycles Crash - Cycles crashes before sampling when certain meshes have autosmooth enabled. #50876