Analytic Lights & Post Processing crashing Octane Server

Sub forum for bug reports
Forum rules
Before posting a bug report, please check the following:
1. That the issue has not already been disclosed
2. That the issue is specific to this plugin, and not Octane in general (Try reproducing it in Standalone)
Bugs related to the Octane Engine itself should be posted into the Standalone Support sub-forum.


All bug reports should include the information below, along with a detailed description of the issue and steps to reproduce it.
A. Operating System, including version (i.e. Win 7, OSX 10.11.2, Ubuntu 14.04, etc.)
B. Graphics Card(s) model (i.e. GTX 580 - 3GB, TITAN, etc.)
C. RAM Capacity (i.e. 6 GB)
D. Nvidia driver version (i.e. 7.50, 7.5.22)
E. OctaneRender Standalone version, if installed (i.e. 2.24.2, 2.23, etc.)
F. OctaneRender plugin version (i.e. v2.25 - 2.21)
G. Host application version, including build number if available (i.e. 3ds Max 2016 Build 18.0)
Post Reply
pegot
Licensed Customer
Posts: 942
Joined: Mon Nov 07, 2011 3:44 am

Big issue with Analytic lights causing some kind of memory error under certain situations. This is happening in Windows version of OctaneBlender and reproduced on two different computers.

I am using an Analytic light set to disc. Octane Server crashes while using Analytic lights with post processing in viewport preview render. The first initiation of viewport render sometimes works fine - one can see the post process effects on the Analytic lights, adjust settings, and freely move around during viewport rendering. However, if one shuts down rendered view by going back into shaded view and after that again attempts a viewport render - server crashes with following error: "ERROR! check console for detailed error message."

Various Errors from Console logs on numerous separate crashes while testing show this:
Octane: ERROR. Server log:

Failed devices:
NVIDIA GeForce RTX 5090(device 0), error message: "CUDA error (700) on device 0: an illegal memory access was encountered -> failed to allocate device memory"

Last Octane engine log entries:
CUDA error (700) on device 1: an illegal memory access was encountered
-> failed to load symbol data to the device(const24)
device 1: failed to upload light parameters for post.
Failed devices:
NVIDIA GeForce RTX 5090(device 0), error message: "CUDA error (700) on device 0: an illegal memory access was encountered -> could not get memory info"

Last Octane engine log entries:
OptiX error for device 1: [ERROR] Failed to copy internal launch buffer (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error recording resource event on user stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
OptiX API error for device 1: CUDA error
device 1: RTX tracing for post failed
CUDA error (700) on device 0: an illegal memory access was encountered
-> could not get memory info
CUDA error (700) on device 0: an illegal memory access was encountered
-> failed to allocate device memory
device 0: failed to allocate post-fx buffer
CUDA error (700) on device 0: an illegal memory access was encountered
-> failed to deallocate device memory
CUDA error (700) on device 0: an illegal memory access was encountered
-> could not get memory info
Failed devices:
NVIDIA GeForce RTX 5090(device 0), error message: "CUDA error (700) on device 0: an illegal memory access was encountered -> could not get memory info"

Last Octane engine log entries:
OptiX error for device 1: [ERROR] Failed to copy internal launch buffer (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
Error recording resource event on user stream (CUDA error string: an illegal memory access was encountered, CUDA error code: 700)
OptiX API error for device 1: CUDA error
device 1: RTX tracing for post failed
CUDA error (700) on device 1: an illegal memory access was encountered
-> failed to load symbol data to the device(const24)
device 1: failed to upload light parameters for post
CUDA error (700) on device 1: an illegal memory access was encountered
-> failed to load symbol data to the device(const24)
device 1: failed to upload light parameters for post
CUDA error (700) on device 0: an illegal memory access was encountered
-> could not get memory info
Strange thing is this issue only happens in viewport render. It doesn’t happen at all in camera render view or final render as long as viewport render hasn't been initiated (or sometimes if it was only initiated once).

The error doesn’t occur on Mac. And I have only tried this with the current stable standard plugin not the add on beta. OctaneBlender version is 2025.3 - 30.7 [STABLE].

Can provide more detailed logs and specs of computers if necessary. Basically, I'm on Windows 10 using a 5090 and a 3090 on main machine and a 3080, 3080 Ti, and a 1080 Ti on the other.

NVIDIA Studio driver 581.29. Just updated to Studio driver 581.57 and issue persists (perhaps even more unstable).

The Mac, which tested fine, is a Mac Mini M1 running Sequoia 15.7.1.

Will post this in Discord channel as well.
Win 10 - AMD Ryzen 9 5950X
MB: ASRock X570 Creator
PSU: 1600w EVGA
5090 MSI Suprim WC
3090 ASUS Tuff
linograndiotoy
OctaneRender Team
Posts: 1391
Joined: Thu Feb 01, 2018 7:10 pm

As you found out, the problem happens only on systems using multiple GPUs. It would be nice to try the same using the addon version and verify if the issue also happens there.
pegot
Licensed Customer
Posts: 942
Joined: Mon Nov 07, 2011 3:44 am

Just tested with addon version and issue doesn't appear to be present there.
Win 10 - AMD Ryzen 9 5950X
MB: ASRock X570 Creator
PSU: 1600w EVGA
5090 MSI Suprim WC
3090 ASUS Tuff
Post Reply

Return to “Bug Reports”