Thanks for your report. We'll fix this!

Yes, we have some issue with the DB in the addon version we need to solve.

Thanks for your report!

No problem here with your file either. Any particular thing I should try to generate the crash?

Seems to work fine here.

Thank you for your reply.

No, I was talking about literally stopping live rendering mode while I'm making changes to the shaders.

I have not tested this feature, which is disabled by default on my side.

Once checked, it no longer displays anything in the render window. Maybe I'm using it ...

As I've mentioned multiple times, Real-Time rendering isn’t a very “safe” option. It disables some important features and can lead to unexpected bugs in certain situations.
My advice is to keep it turned off while doing serious work.

Does this always happen or is related to a specific scene?

I just tested this on the PC version, and memory usage looks normal, as you can see:

Screenshot 2025-08-15 101947.png

I turned the Octane preview on and off three times, and memory consumption remained stable.

This seems to be a Mac-specific issue, so I’ll point the developers to this thread ...

Important note: DO NOT USE VULKAN FOR NOW.

Hi!
I don't have a mac to test the build, but the "missing paths" is just normal as long as you didn't create any preset. About the LiveDB, did you set the Path in the Octane Addon Preferences?