Compilation error: (OutOfMemoryException: Out of memory)Not An Issue
Thanks!

I know a major chance of subject but evrey now and then my server crashes, its claimed to be a memory error but I just want you smart poeple to conferm that its memory alone :)

it happens after a plugin install or plugin reload:

Compilation error: (OutOfMemoryException: Out of memory)

at (wrapper managed-to-native) System.Object.__icall_wrapper_ves_icall_array_new_specific(intptr,int)

at System.IO.MemoryStream.set_Capacity (System.Int32 value) [0x00057] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.IO.MemoryStream.EnsureCapacity (System.Int32 value) [0x00061] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.IO.MemoryStream.Write (System.Byte[] buffer, System.Int32 offset, System.Int32 count) [0x000b3] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.IO.BinaryWriter.Write (System.Byte[] buffer) [0x0000e] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.__BinaryWriter.WriteBytes (System.Byte[] value) [0x00000] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.__BinaryWriter.WriteSingleArray (System.Runtime.Serialization.Formatters.Binary.NameInfo memberNameInfo, System.Runtime.Serialization.Formatters.Binary.NameInfo arrayNameInfo, System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo objectInfo, System.Runtime.Serialization.Formatters.Binary.NameInfo arrayElemTypeNameInfo, System.Int32 length, System.Int32 lowerBound, System.Array array) [0x000ac] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.__BinaryWriter.WriteObjectByteArray (System.Runtime.Serialization.Formatters.Binary.NameInfo memberNameInfo, System.Runtime.Serialization.Formatters.Binary.NameInfo arrayNameInfo, System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo objectInfo, System.Runtime.Serialization.Formatters.Binary.NameInfo arrayElemTypeNameInfo, System.Int32 length, System.Int32 lowerBound, System.Byte[] byteA) [0x00006] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.WriteArray (System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo objectInfo, System.Runtime.Serialization.Formatters.Binary.NameInfo memberNameInfo, System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo memberObjectInfo) [0x0018f] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write (System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo objectInfo, System.Runtime.Serialization.Formatters.Binary.NameInfo memberNameInfo, System.Runtime.Serialization.Formatters.Binary.NameInfo typeNameInfo) [0x00056] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize (System.Object graph, System.Runtime.Remoting.Messaging.Header[] inHeaders, System.Runtime.Serialization.Formatters.Binary.__BinaryWriter serWriter, System.Boolean fCheck) [0x001d3] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize (System.IO.Stream serializationStream, System.Object graph, System.Runtime.Remoting.Messaging.Header[] headers, System.Boolean fCheck) [0x0006e] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize (System.IO.Stream serializationStream, System.Object graph, System.Runtime.Remoting.Messaging.Header[] headers) [0x00000] in <ac823e2bb42b41bda67924a45a0173c3>:0

at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize (System.IO.Stream serializationStream, System.Object graph) [0x00000] in <ac823e2bb42b41bda67924a45a0173c3>:0

at ObjectStream.IO.ObjectStreamWrapper`2[TRead,TWrite].Serialize (TWrite obj) [0x00006] in <9affce1cd15c4ec183941adef8db1722>:0

at ObjectStream.IO.ObjectStreamWrapper`2[TRead,TWrite].WriteObject (TWrite obj) [0x00000] in <9affce1cd15c4ec183941adef8db1722>:0

at ObjectStream.ObjectStreamConnection`2[TRead,TWrite].WriteStream () [0x00021] in <9affce1cd15c4ec183941adef8db1722>:0

at ObjectStream.Threading.Worker.DoWorkImpl (System.Object oAction) [0x00007] in <9affce1cd15c4ec183941adef8db1722>:0



whould have asked my host if it wasn't becuse they are useless.

That error would mean that the compiler doesn't have enough memory available for it to run. The compiler generally only uses 100mb of memory.
Yeah this is a problem huh?
In response to TactiTac0z ():
Yeah this is a problem huh?
What is a problem exactly?

The machine setup needs to provide enough memory for the compiler to run, otherwise you will see errors like the above one. It takes barely any memory to run the compiler, which that compiler has been the same compiler we've used for years without issues. I'd suggest checking with your host to see if there may be some sort of restriction on your server's memory usage and allocations of it. The same would apply to the server itself; no memory available = likely to crash.
The proof of compiler taking almost no memory (107MB) 
In response to 2CHEVSKII ():
The proof of compiler taking almost no memory (107MB) 
Tell that to my server provider why don't you?
In response to TactiTac0z ():
Tell that to my server provider why don't you?
Maybe because I don't even know what is your SP?
Locked automatically