2.15 failed to deallocate device memory

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
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

here is error I got
I noticed after stopping rendering, going back to octane viewport, then rendering like 5 frames going back ... but after everything was adjusted and final rendering started i got this message after 3rd frame
Attachments
octane 2.15 141215 224711.log
(11.24 KiB) Downloaded 335 times
User avatar
abstrax
OctaneRender Team
Posts: 5506
Joined: Tue May 18, 2010 11:01 am
Location: Auckland, New Zealand

coilbook wrote:here is error I got
I noticed after stopping rendering, going back to octane viewport, then rendering like 5 frames going back ... but after everything was adjusted and final rendering started i got this message after 3rd frame
The first CUDA error is the problem: For some reason the direct lighting kernel failed. If you can reproduce this problem, please send us the scene so we can investigate. Thanks.
In theory there is no difference between theory and practice. In practice there is. - Yogi Berra
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

thank you i will
i noticed scenes that load to memory fast crash a lot more often than the ones that takes awhile i guess cards get too hot.

Before i had a scene where it took 30-50 seconds just to load the scene before rendering. So really card had 30-50 seconds break time to cool off and it never had cuda errors .

This scene loads within seconds and i guess cards get too hot even 65C I guess is too much for GPU even though it is supposed to work up to 90C

is it possible to create like a 'break time schedule' where I can tell rednerer to stop after 30 minutes of rendering for 2 minutes to cool cards off and resume rendering. Would be nice for overnight renderings. or if it stops with cuda error Auto restart itself after a minute.

thank you
User avatar
face_off
Octane Plugin Developer
Posts: 15693
Joined: Fri May 25, 2012 10:52 am
Location: Adelaide, Australia

Have you tried backing off the clock speeds of your cards a little?
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

face_off wrote:Have you tried backing off the clock speeds of your cards a little?
i just did i think it helped
Seems like it became more stable and render time stayed the same I thought it would be slower
Thank you
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

some lost samples on slave in 2.15
Attachments
octane 2.15 141216 132515.log
(7.07 KiB) Downloaded 335 times
User avatar
face_off
Octane Plugin Developer
Posts: 15693
Joined: Fri May 25, 2012 10:52 am
Location: Adelaide, Australia

Seems like it became more stable and render time stayed the same I thought it would be slowe
I had a card which did a similar thing. I think it's a hardware fault - when the clock speed is too high the render starts too quickly and "something" on the card is not up to speed so it fails. Different versions of Octane have fractionally different start times, so some are effected by the problem more than others. I'm sure there is a more technical explanation for this. An Octane configurable "delay" might help with this.

Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

face_off wrote:
Seems like it became more stable and render time stayed the same I thought it would be slowe
I had a card which did a similar thing. I think it's a hardware fault - when the clock speed is too high the render starts too quickly and "something" on the card is not up to speed so it fails. Different versions of Octane have fractionally different start times, so some are effected by the problem more than others. I'm sure there is a more technical explanation for this. An Octane configurable "delay" might help with this.

Paul
you might be right
because it started after installed second card 980 (I have one is 780 TI and one is 980). And it runs at a lot higher speed than 780 TI
coilbook
Licensed Customer
Posts: 3032
Joined: Mon Mar 24, 2014 2:27 pm

if it help all cards are classified evga with acx cooling and bigger board
Post Reply

Return to “Bug Reports”