Render crashes when linked objects #80314

New Issue

Joselu · 2020-09-01T09:05:49+02:00

Joselu commented

2020-09-01 09:05:49 +02:00

Render crashes. Open file GARDEN Final Scene and press F12. Only when removing linked objects it works.

Zip file includes all files needed and System Info.GARDEN Final Scene Render CRASH.zip

Render crashes. Open file GARDEN Final Scene and press F12. Only when removing linked objects it works. Zip file includes all files needed and System Info.[GARDEN Final Scene Render CRASH.zip](https://archive.blender.org/developer/F8828842/GARDEN_Final_Scene_Render_CRASH.zip)

Joselu commented

2020-09-01 09:05:49 +02:00

Added subscriber: @Xeluaxeman

Germano Cavalcante commented

2020-09-02 22:02:06 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2020-09-02 22:02:06 +02:00

It didn't crash here, but I also can't render with GPU because this OpenCL error:

OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114)
OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114)
OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114)
OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114)
OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:99)
OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:99)
Error: OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114)

I don't know what can lead to this error, but apparently it is a memory problem, which is not surprising since this file is very complex.
For valid bug reports it is recommended that the file be simplified to the maximum. This makes it easy to identify the problem.

If an out-of-memory problem is confirmed, this is not considered a bug, but a hardware limitation.

It didn't crash here, but I also can't render with GPU because this OpenCL error: ``` OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114) OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114) OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114) OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114) OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:99) OpenCL error: CL_INVALID_VALUE in clEnqueueWriteBuffer(device->cqCommandQueue, CL_MEM_PTR(new_buffer->device_pointer), CL_FALSE, offset, allocation->mem->memory_size(), allocation->mem->host_pointer, 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:99) Error: OpenCL error: CL_INVALID_VALUE in clEnqueueCopyBuffer(device->cqCommandQueue, CL_MEM_PTR(buffer->device_pointer), CL_MEM_PTR(new_buffer->device_pointer), allocation->desc.offset, offset, allocation->mem->memory_size(), 0, NULL, NULL) (C:\Germano\Dev\BlenderDev\blender\intern\cycles\device\opencl\memory_manager.cpp:114) ``` I don't know what can lead to this error, but apparently it is a memory problem, which is not surprising since this file is very complex. For valid bug reports it is recommended that the file be simplified to the maximum. This makes it easy to identify the problem. If an out-of-memory problem is confirmed, this is not considered a bug, but a hardware limitation.

Joselu commented

2020-09-03 09:52:47 +02:00

This scene rendered without problems in 2.8.
It is a project i left unfinished but had no problems until opened in 2.9 for testing pupouses.
All is optimized and i am sure it is not hardware limitation.
I think i could add more objects to the scene in 2.8 and will render.

This scene rendered without problems in 2.8. It is a project i left unfinished but had no problems until opened in 2.9 for testing pupouses. All is optimized and i am sure it is not hardware limitation. I think i could add more objects to the scene in 2.8 and will render.

Joselu commented

2020-09-03 12:57:56 +02:00

Confirmed. In 2.83.5 you can even add plenty of geometry and external objects and works fine.

Steffen Dünner commented

2020-09-03 13:01:34 +02:00

Added subscriber: @SteffenD

Steffen Dünner commented

2020-09-03 13:01:34 +02:00

Just gave this scene a try and it renders without problems here:

Just gave this scene a try and it renders without problems here: ![image.png](https://archive.blender.org/developer/F8836048/image.png)

Germano Cavalcante commented

2020-09-03 14:28:05 +02:00

@Xeluaxeman, rendering with CPU or GPU?
Have you tried Optix, Cuda and OpenCL?

@Xeluaxeman, rendering with CPU or GPU? Have you tried Optix, Cuda and OpenCL?

Joselu commented

2020-09-03 16:19:39 +02:00

CUDA of course. I guess something went wrong from 2.8 to 2.9. I will make some more tests but 2.9 is unstable in my case and will only keep 2.8 files until the issue is fixed.

Steffen Dünner commented

2020-09-03 17:06:43 +02:00

What caught my eye when giving this scene a try was that your hair rendering geometry was set to:
which is a major difference to 2.83

Not sure if that's the culprit though.
Maybe you could give "Rounded Ribbons" with "Curve Subdivisions" of 2 a try?

What caught my eye when giving this scene a try was that your hair rendering geometry was set to:![image.png](https://archive.blender.org/developer/F8836503/image.png) which is a major difference to 2.83 Not sure if that's the culprit though. Maybe you could give "Rounded Ribbons" with "Curve Subdivisions" of 2 a try?

Richard Antalik commented

2020-09-03 20:24:51 +02:00

Added subscriber: @iss

Richard Antalik commented

2020-09-03 20:24:51 +02:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Richard Antalik commented

2020-09-03 20:24:51 +02:00

@Xeluaxeman what is your OS? Can you update GPU drivers?
Does this happen, when you click on File > Load Factory Settings, load your file and render?

Please update report description with OS and GPU info and worked/broken version. Click on Help > Report a Bug to auto fill in this info.

Finally your file is too big to really debug. You should remove as much objects as possible while making sure bug is still there. If this is not out-of-memory problem, crash is probably caused by one object.

@Xeluaxeman what is your OS? Can you update GPU drivers? Does this happen, when you click on File > Load Factory Settings, load your file and render? Please update report description with OS and GPU info and worked/broken version. Click on Help > Report a Bug to auto fill in this info. Finally your file is too big to really debug. You should remove as much objects as possible while making sure bug is still there. If this is not out-of-memory problem, crash is probably caused by one object.

Joselu commented

2020-09-04 02:25:50 +02:00

Sorry everybody. Linked file Candle Final that has pre cached fluids for the flame is the problem.
Thanks. I will keep testing 2.9.

Sorry everybody. Linked file Candle Final that has pre cached fluids for the flame is the problem. Thanks. I will keep testing 2.9.

Richard Antalik commented

2020-09-07 06:09:08 +02:00

Does that mean that you have resolved the problem by clearing caches?

Joselu commented

2020-09-07 09:48:25 +02:00

Yes. Linked objects have some limitations with fluids cache by now.
No problem since i only link unfinished objects as a preview for the whole scene. I would use imported objects for animation purpouses once all final setups are done.

Yes. Linked objects have some limitations with fluids cache by now. No problem since i only link unfinished objects as a preview for the whole scene. I would use imported objects for animation purpouses once all final setups are done.

Ankit Meel commented

2020-09-07 22:26:35 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2020-09-07 22:26:35 +02:00

Could you make a simple blend file from scratch that could help us test this issue with linked objects ?

Philipp Oeser commented

2020-10-12 11:42:40 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2020-10-12 11:42:40 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Philipp Oeser closed this issue

2020-10-12 11:42:40 +02:00

Philipp Oeser self-assigned this 2020-10-12 11:42:40 +02:00

Philipp Oeser commented

2020-10-12 11:42:40 +02:00

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.

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.

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

Render crashes when linked objects #80314