Page 1 of 1

OctaneServer 2026.1 (31.3 Beta) crashes on second render (ACCESS_VIOLATION)

Posted: Mon Mar 09, 2026 7:36 am
by Faildozer
OctaneServer Studio 2026.1 (31.3 beta) crashes with an ACCESS_VIOLATION (0xc0000005) in octane.dll when rendering a second time. The first render typically completes successfully, but any subsequent render causes OctaneServer to crash. This affects both viewport rendering and final (F12) rendering.

Environment
OS: Windows 10 Pro 22H2 (Build 19045)
GPU: NVIDIA GeForce RTX 4090
Driver: 591.74 (CUDA 13.1)
OctaneServer: 2026.1 Studio Edition (31.3 beta), downloaded from viewtopic.php?t=85465
Blender: 5.0 with OctaneBlender addon v31.3.0

Same issue on my second machine with more recent drivers.


OctaneServer crashes on the second render. Windows Event Viewer consistently reports:

Code: Select all

Faulting application name: OctaneServer.exe, version: 0.0.0.0
Faulting module name: octane.dll, version: 15.0.0.9
Exception code: 0xc0000005 (ACCESS_VIOLATION)


Using Sysinternals ProcDump (procdump64.exe -e 1 -f "C0000005" -ma OctaneServer.exe), the following exception sequence was captured:

Code: Select all

[08:35:12] Exception: E06D7363.?AVinterprocess_exception@interprocess@boost@@
[08:35:53] Exception: E06D7363.?AVinterprocess_exception@interprocess@boost@@
[08:41:53] Exception: C0000005.ACCESS_VIOLATION
[08:41:53] Dump 1 initiated: OctaneServer.exe_260306_084153.dmp
[08:41:53] Dump 1 writing: Estimated dump file size is 7573 MB.
[08:42:14] Dump 1 complete: 7574 MB written in 20.7 seconds
The two boost::interprocess::interprocess_exception exceptions occur during Blender's initial connection to OctaneServer, the ACCESS_VIOLATION occurs during the second render and is unhandled, causing the crash. a 7.5 GB memory dump was captured and is available upon request.


CPU Registers at Crash

Code: Select all

RIP: 0x00007ffc91b2c74b  -> octane.dll+0xb0c74b
RSP: 0x000000997f9fe5f0
RBP: 0x000000997f9fe710
RAX: 0x0000000000000000  (NULL)
RBX: 0x0000022bc0068590  (valid heap pointer)
RCX: 0x0000000000000000  (NULL - "this" pointer in MSVC x64)
RDX: 0x00007ff7a2bef790  -> OctaneServer.exe+0xcf790
RSI: 0xcbf29ce484222325  (looks like an FNV-1a hash constant)
R9:  0x00000200022c0298  (garbage index too large for any array)
R14: 0x0000022bf9999630  (valid heap pointer)
R15: 0x0000022bf988edb0  (valid heap pointer)
ASM

Code: Select all

octane.dll+0xb0c74b:  mov rcx, [rbx + r9*8]   ; <-- CRASH array/hash table lookup
octane.dll+0xb0c74f:  cmp rcx, r8             ; compare
octane.dll+0xb0c752:  je  0xb0c82e            ; branch
Hope this helps.

Re: OctaneServer 2026.1 (31.3 Beta) crashes on second render (ACCESS_VIOLATION)

Posted: Tue Mar 10, 2026 9:35 am
by linograndiotoy
In which situation does it crash?

We're about to release a new build, by the way.

Please test it and let us know.

Re: OctaneServer 2026.1 (31.3 Beta) crashes on second render (ACCESS_VIOLATION)

Posted: Tue Mar 10, 2026 11:43 am
by Faildozer
I'm building a fairly large scene. When i render the scene the first time it works, either viewport or f12, but the second time i try to render again, either viewport or f12 it always crashes. I'll hold out for the new build and try that and if I'm still having issues i can send the scene/dumps if you'd like.