Page MenuHome

Blender crash when using Edit mode for Ocean
Closed, ResolvedPublic

Description

System Information
Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 770/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 398.82

Blender Version
Broken: version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e
Worked: (optional)

Short description of error
Blender crash when using Edit mode for Ocean

Exact steps for others to reproduce the error

Related Objects

Event Timeline

Under 2.79 the file run .
I tried many times under 2.80

I can confirm. Doesn't crash when both windows are in Solid mode.

Operating system: Windows-10-10.0.18362 64 Bits
Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 436.15

Broken: version: 2.81 (sub 4), branch: master, commit date: 2019-08-31 11:22, hash: rB82ef1edce4a2

Philipp Oeser (lichtwerk) renamed this task from Blender crash to Blender crash when using Edit mode for Ocean.Aug 31 2019, 11:31 PM

error on crashing:

Error	: EXCEPTION_ACCESS_VIOLATION
Address	: 0x00007FF79E9C8EA3
Module	: C:\Users\MaqboolStudio-PC\Downloads\Compressed\blender-2.81-883706395ee3-win64\blender-2.81.0-git.883706395ee3-windows64\blender.exe

Note: Seems, material causes crash (when remove no crash):

Hum! Attribute dp_wetmap causing crash...


Can't find attribute, on other place, maybe cause of crash...
Note: If you remove text dp_wetmap, no crash at all

Thanks

Dalai Felinto (dfelinto) lowered the priority of this task from Needs Triage by Developer to Needs Information from User.Sep 19 2019, 2:15 AM

@cosquer (jakez27) thanks for the report, I have a few questions for you:

  1. Could you reproduce this from scratch in 2.80?
  2. How about a 2.79 file opened in 2.80?
  3. Which version of Blender you used to save the file the last time?

Crash related information:

BLI_assert failed: //source/blender/blenkernel/intern/customdata.c:2074, CustomData_get_layer_index_n(), at 'i + n < data->totlayer'
Full backtrace: P1107

Bastien Montagne (mont29) raised the priority of this task from Needs Information from User to Confirmed, Medium.

Think that one is for @Clément Foucault (fclem), at least as a first step? Looks like the mesh from MeshRenderData in extract_vcol_init() does not have the expected data? loop cddata only have three layers, a UV (when orig mesh has none?), a VCol (foam, generated by the Ocean modifier), and the loops themselves…

Crash itself happens just after since CustomData_get_layer_name() finds no valid layer, it returns a NULL name, and extract_vcol_init() does not take care of that case at all.

Clément Foucault (fclem) raised the priority of this task from Confirmed, Medium to Confirmed, High.Mon, Oct 7, 8:00 PM