<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: OUT_OF_MEMORY errors on Flame 2019.1 in Flame Forum</title>
    <link>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8858943#M3286</link>
    <description>&lt;P&gt;Looks like, for us, leaving it at 90% has helped with the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems to be running fine now.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the help, Jeffrey!&lt;/P&gt;</description>
    <pubDate>Tue, 18 Jun 2019 23:13:48 GMT</pubDate>
    <dc:creator>TimberVFX</dc:creator>
    <dc:date>2019-06-18T23:13:48Z</dc:date>
    <item>
      <title>OUT_OF_MEMORY errors on Flame 2019.1</title>
      <link>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8852843#M3282</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We are encountering multiple issues with Flame 2019.1 and getting an OUT_OF MEMORY on different comps when, what it seems like at the moment, using sapphire plugins.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Machine is z840 and has 64GB of memory, with one Nvidia Quadro M6000 and runnind DKU 13.2.0. Also running the latest Sapphire plugins which is 2019. It seems to have happen with older versions of sapphire as well, I just updated thinking it might be it was just running an older version of the plugin. But it seems to still lock up the flame with the new version.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is the output of the flame shell logs:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Jun 14 13:07:26 : dlCheckGLError: GL_INVALID_VALUE&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:10:18 : Loading: S_EdgeFlash, Version 2019.04 (x86_64), D48P40.32.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:10:18 : GPU accelerated&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:10:18 : Loading: S_EdgeBlur, Version 2019.04 (x86_64), D48P40.32.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:10:18 : GPU accelerated&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:10:19 : Loading: S_GlareMask, Version 2019.04 (x86_64), D48P40.32.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:10:19 : GPU accelerated&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:11:34 : dlCheckGLError: Texture::reset()&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:11:34 : dlCheckGLError: GL_INVALID_OPERATION&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:12:19 : Connect sequence failed at preconnect stage&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:13:43 : Loading: S_EdgeFlash, Version 2019.04 (x86_64), D48P40.32.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:13:43 : GPU accelerated&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:14:26 : Loading: S_GlareMask, Version 2019.04 (x86_64), D48P40.32.&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:14:26 : GPU accelerated&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : OUT_OF_MEMORY&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : cc312 : OUT_OF_MEMORY&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : transform2d346 : cc312 : OUT_OF_MEMORY&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : ADD_JITTER765 : transform2d346 : cc312 : OUT_OF_MEMORY&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : cc1142 : ADD_JITTER765 : transform2d346 : cc312 : OUT_OF_MEMORY&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : comp281 : cc1142 : ADD_JITTER765 : transform2d346 : cc312 : OUT_OF_MEMORY&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : cc272 : comp281 : cc1142 : ADD_JITTER765 : transform2d346 : cc312 : OUT_OF_MEMORY&lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;Jun 14 13:16:00 : comp284 : cc272 : comp281 : cc1142 : ADD_JITTER765 : transform2d346 : cc312 : OUT_OF_MEMORY&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone seen this before or have quick fix for it?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thanks in advanced.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jun 2019 21:13:09 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8852843#M3282</guid>
      <dc:creator>TimberVFX</dc:creator>
      <dc:date>2019-06-14T21:13:09Z</dc:date>
    </item>
    <item>
      <title>Re: OUT_OF_MEMORY errors on Flame 2019.1</title>
      <link>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8852881#M3283</link>
      <description>&lt;P&gt;We just disabled gpu acceleration thinking it might something to do with the way sparks are interacting with the GFX card, but no dice. It still gives me the same error&amp;nbsp; and crashes flame:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Jun 14 14:36:25 : Output log to: '/opt/Autodesk/log/slateDiskCacheCleaner.log'.&lt;BR /&gt;Jun 14 14:36:31 : Loading: S_EdgeFlash, Version 2019.04 (x86_64), D48P40.32.&lt;BR /&gt;Jun 14 14:37:41 : Loading: S_EdgeFlash, Version 2019.04 (x86_64), D49P40.32.&lt;BR /&gt;Jun 14 14:37:59 : Loading: S_GlareMask, Version 2019.04 (x86_64), D48P40.32.&lt;BR /&gt;Jun 14 14:38:12 : dlCheckGLError: Texture::reset()&lt;BR /&gt;Jun 14 14:38:12 : dlCheckGLError: GL_INVALID_OPERATION&lt;BR /&gt;Jun 14 14:38:13 : OUT_OF_MEMORY&lt;BR /&gt;Jun 14 14:38:13 : cc130 : OUT_OF_MEMORY&lt;BR /&gt;Jun 14 14:38:13 : comp131 : cc130 : OUT_OF_MEMORY&lt;BR /&gt;Jun 14 14:38:13 : transform2d309 : comp131 : cc130 : OUT_OF_MEMORY&lt;BR /&gt;Jun 14 14:38:13 : transform2d264 : transform2d309 : comp131 : cc130 : OUT_OF_MEMORY&lt;BR /&gt;Jun 14 14:38:13 : action290 : transform2d264 : transform2d309 : comp131 : cc130 : OUT_OF_MEMORY&lt;BR /&gt;Jun 14 14:38:13 : cc312 : action290 : transform2d264 : transform2d309 : comp131 : cc130 : OUT_OF_MEMORY&lt;/P&gt;</description>
      <pubDate>Fri, 14 Jun 2019 21:43:42 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8852881#M3283</guid>
      <dc:creator>TimberVFX</dc:creator>
      <dc:date>2019-06-14T21:43:42Z</dc:date>
    </item>
    <item>
      <title>Re: OUT_OF_MEMORY errors on Flame 2019.1</title>
      <link>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8854501#M3284</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Have you tried adjusting the Memory and Graphics consumption from the Flame Setup? See if it will improve if you adjust to higher percentage, (~80%).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Jeff&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2019 02:30:30 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8854501#M3284</guid>
      <dc:creator>jeffrey.ramirez</dc:creator>
      <dc:date>2019-06-17T02:30:30Z</dc:date>
    </item>
    <item>
      <title>Re: OUT_OF_MEMORY errors on Flame 2019.1</title>
      <link>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8855922#M3285</link>
      <description>&lt;P&gt;Hi Jeffrey,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I actually set the graphics memory threshold down to 90% on Friday to see if it would help, I ran my tests on it and it seemed to be stable, but the artist unfortunately jumped to another flame since he needed to finish a few shots for delivery that night. I am going to have him replicate the issue today and will report back if 90% works or if i need to drop it down to 80%.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The system memory seems to be fine, it stays between 32GB used out of the 64GB installed on these comps/shots, so I didn't adjust that.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you for the reply and will keep you informed.&lt;/P&gt;</description>
      <pubDate>Mon, 17 Jun 2019 17:25:37 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8855922#M3285</guid>
      <dc:creator>TimberVFX</dc:creator>
      <dc:date>2019-06-17T17:25:37Z</dc:date>
    </item>
    <item>
      <title>Re: OUT_OF_MEMORY errors on Flame 2019.1</title>
      <link>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8858943#M3286</link>
      <description>&lt;P&gt;Looks like, for us, leaving it at 90% has helped with the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It seems to be running fine now.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks for the help, Jeffrey!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2019 23:13:48 GMT</pubDate>
      <guid>https://forums.autodesk.com/t5/flame-forum/out-of-memory-errors-on-flame-2019-1/m-p/8858943#M3286</guid>
      <dc:creator>TimberVFX</dc:creator>
      <dc:date>2019-06-18T23:13:48Z</dc:date>
    </item>
  </channel>
</rss>

