Exception while starting compiler, out of memoryNot An Issue

Exception while starting compiler version : (Win32Exception: ApplicationName='/home/rustserver/serverfiles/Compiler.x86_x64', CommandLine='/service /logPath:/home/rustserver/serverfiles/oxide/logs', CurrentDirectory='', Native error= Out of memory) at System.Diagnostics.Process.StartWithCreateProcess (System.Diagnostics.ProcessStartInfo startInfo) [0x002dc] in <3845a180c26b4889bc2d47593a665814>:0 at System.Diagnostics.Process.Start () [0x0003a] in <3845a180c26b4889bc2d47593a665814>:0 at (wrapper remoting-invoke-with-check) System.Diagnostics.Process.Start() at Oxide.Plugins.PluginCompiler.CheckCompiler () [0x001f3] in <9affce1cd15c4ec183941adef8db1722>:0 (21:11:31) | Compiler may not be set as executable; chmod +x or 0744/0755 required (21:11:31) | Win32 NativeErrorCode: 14 ErrorCode: -2147467259 HelpLink: (21:11:31) | Error while compiling: compiler version couldn't be started

Hi,

I'm seeing the above error when trying to restart any plugin on my server.  Current RAM usage is 6.2gb/8gb - surely that's enough spare for the compiler?  I've double checked the permissions on the compiler and it's 0755 for the user that runs the server.

Any idea?

Cheers

Your server ran out of memory, we do not control that and it only uses what is available to it. The compiler only requires 100mb max.
In response to Wulf ():
Your server ran out of memory, we do not control that and it only uses what is available to it. The...
Current RAM usage is 6.2gb/8gb -- it's not out of memory though.
In response to myles91 ():
Current RAM usage is 6.2gb/8gb -- it's not out of memory though.
It would have been at the time the compiler was trying to grab some; what may be available to the server isn't necessarily what you may see on panels either, hard to say.
Regardless of what your total RAM usage is, the error is a low level error that states
Native error = Out of memory
Low level errors like this can be caused by different kinds of memory (not just your motherboards RAM) and they are usually fixed by system administrators.  There isn't really anything we can do to the current Compiler to prevent an "Out of memory" error like this.

Some things to look into..
VRAM (usually a client issue though),
Swap (harddisk) memory
Virtualization memory limits (if using virtualization)
Locked automatically