RAM drive not available again in lucee(RAM error)

Please always state which version! :slight_smile:

Ahh sorry, this is an old ticket and no fix, so I presume it’s on all versions.
I’m running 5.3.4.80.

I write temporary files with UUID filenames onto the RAM drive. Not often, maybe a couple of times a day. Each probably < 5kb.
Occasionally I get an error like: can't write file [ram:///CFBEFFC33FD81DABE8D322E0BD5A5C70] as a file, missing parent directory [ram://]

A restart of the service often fixes for a while… so it sounds like the same issue to me.
I’ve updated the code to use the physical filesystem now.

in your use case, would a (short lived) i.e. session based ram drive be useful?

Only if it acts as a filesystem. The resulting file is used with a <cfinclude> and a mapping to the RAM drive.

We do have the same issue on two of our server with Lucee v 5.3.6.61:

can’t write file [ram:///menu_main.xml] as a file, missing parent directory [ram://]

Restart of the Lucee Service fixes the problem for a while.

1 Like

Same here. Just popped up after upgrading to the latest Lucee 5.3.8.206 after being on the July 2019 release for… well, two years+. Looking at the memory charts on the Overview page I’m between 26% and 43% Heap, 12% Non-Heap. A restart of the Lucee/Tomcat service cleared up the error, but as William Shatner says “for how long? For… how… long?”

I’m using the QRCode.cfc (Sept 2018 latest version), which uses the 2019 version of itext.