Page MenuHome

Crash in cycles with volume and displacement
Closed, ArchivedPublic

Description

System Information
Operating system: macOS 11.2.2
Graphics card: (none available on Mac)

Blender Version
Broken: 2.93
Worked: Note sure pricely, but alphas/betas of same (I've been tweaking the scene).

Short description of error
Application crash (see attached)

Exact steps for others to reproduce the error
Based on below .blend file
Clicking materials properties (the preview for which stays black), then adjusting things leads to a crash. In the below example, adjusting the volume step rate on the Mars - clouds object from 0.1 to 0.2 was sufficient. I do not know how to simplify this file - seems like it may be resource related, but I've got 64GB of RAM, so if it is a memory, seems we're not handling that ideally.

https://www.dropbox.com/s/a1czpwk9obsjvnl/Mars-packed.blend?dl=0

Event Timeline

Evan Wilson (EAW) changed the task status from Needs Triage to Needs Information from User.Jun 9 2021, 4:29 AM

Thank you for the report. Right before the crash, Blender is calling Color Management functions.

4   Blender                             0x0000000103ac5f46 _ZN8OCIOImpl27cpuProcessorApply_predivideEPP29OCIO_ConstCPUProcessorRcPtr__PP22OCIO_PackedImageDesc__ + 198
5   Blender                             0x0000000102c43106 IMB_colormanagement_processor_apply + 390
6   Blender                             0x0000000102c3fb6c IMB_colormanagement_transform + 108
7   Blender                             0x0000000102c3fadf colormanage_imbuf_make_linear + 143
8   Blender                             0x0000000102c57163 IMB_ibImageFromMemory + 307
9   Blender                             0x00000001026aa99a load_image_single + 154
10  Blender                             0x00000001026aa2b3 image_load_image_file + 835
11  Blender                             0x00000001026a6ba5 image_acquire_ibuf + 1221
12  Blender                             0x000000010269fbed BKE_image_acquire_ibuf + 45
13  Blender                             0x0000000102ef8c62 Image_size_get + 34
14  Blender                             0x0000000103c35991 _ZN3ccl18BlenderImageLoader13load_metadataERKNS_19ImageDeviceFeaturesERNS_13ImageMetaDataE + 33
15  Blender                             0x00000001048b5815 _ZN3ccl12ImageManager19load_image_metadataEPNS0_5ImageE + 197

Is there a packed image in your file? If so, what happens if you unpack it? Does the crash still occur if you remove all images from the scene?

Also, Are you using a different OCIO configuration file from the default?

Pratik Borhade (PratikPB2123) renamed this task from Crash in cycleas with volume and displacement to Crash in cycles with volume and displacement.Jun 9 2021, 7:42 AM

There are images in it - a surface color map, a cloud grayscale map, and an elevation grayscale map. The entire scene is dependent on the maps (it's a terraformed Mars setup), so it won't render properly at all without the images. Whether they're packed or not makes no difference here (they were originally kept unpacked due to size, I packed them solely for posting here). I have not touched OCIO at all.

Evan Wilson (EAW) changed the task status from Needs Information from User to Needs Triage.Jun 9 2021, 7:47 PM

Removing the images (just X-ing them in the image texture nodes) does clear the crash. Going to purge the blend, reload Blender, and try re-adding them.

This comment was removed by Sean Robertson (seanr).

Added images back and got a crash trying to render, though not sure if it's exactly related to the material properties crash:

That being the Mac error report (which didn't come up before, had to use the CLI to get anything the for the previous one).

Output when running it from CLI - why so much smaller?

Again, as with the OS report, this is a full render.

Philipp Oeser (lichtwerk) changed the task status from Needs Triage to Needs Information from User.Sep 6 2021, 3:37 PM

Hi and thx for the report (sorry it took a while to answer).
Unfortunately the dropbox link to the reproduction .blend seems to be dead, can you put it up again?

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

Thanks again for the report. If the problem persists please open a new report with the required information.