Difference between revisions of "LlGetFreeMemory"
m (Word duplication)
|Line 7:||Line 7:|
This function's behavior is dependent upon the VM the script is using. [[#Mono|Mono]] is the new VM, [[#LSO|LSO]] is the old VM. The big difference
This function's behavior is dependent upon the VM the script is using. [[#Mono|Mono]] is the new VM, [[#LSO|LSO]] is the old VM. The big difference between Mono and LSO is that Mono scripts run faster and can utilize four times more memory.
Latest revision as of 05:58, 19 July 2020
|LSL Portal||Functions | Events | Types | Operators | Constants | Flow Control | Script Library | Categorized Library | Tutorials|
This function's behavior is dependent upon the VM the script is using. Mono is the new VM, LSO is the old VM. The big difference between Mono and LSO is that Mono scripts run faster and can utilize four times more memory.
In Mono the value returned is the amount of free memory available to the script prior to garbage collection being run. This means that memory that is awaiting garbage collection counts against the scripts 64KiB allotment. In addition to this, Mono does not enforce the memory restrictions as strictly as the LSO VM did (with LSO it was impossible to exceed the 16KiB memory cap), consequently it is possible to utilize more of the free memory.
In LSO, the value returned by this function is the amount of memory that the Stack can use of the Heap has yet to allocate for itself.
The LSL memory space is divided into four sections: Byte-code, Stack, Free Memory, Heap. Free Memory isn't an allocated block of memory, it's just the space between Stack and Heap. The size of all four sections combined is 16384 bytes (16KiB).
As the script executes the Stack grows and shrinks in size depending upon the complexity of the expressions being executed. Likewise the Heap grows as the script executes but unlike the Stack, it never shrinks in size. When there is no free memory left for Stack or Heap to use they collide and a Stack-Heap Collision error is thrown causing the script to crash.
The Heap can become fragmented and blocks of memory in it can become unusable (due to their size). There is no defragment function but there are scripting techniques that can be used to reduce fragmentation.
Calling llGetFreeMemory can look like this:
integer free_memory = llGetFreeMemory(); llOwnerSay((string)free_memory + " bytes of free memory available for allocation.");
See also: the "Script run-time error" "Stack-Heap Collision" among the LSL Errors
LSO VM Notes
This function does not count free memory, and the name of this function makes this function difficult for people to learn. People say this function may be redefined or superseded by another more useful function when the LSL VM moves to Mono.
We can concisely specify llGetFreeMemory in the context of the classic Unix model for a parallel task/ thread/ process. Think of the task of the script always holding 16384 bytes (16 KiB). Let the byte code and then stack grow up from the bottom, let the heap grow down from the top. llGetFreeMemory then returns the "historic lowest heap pointer minus the stack end pointer".
llGetFreeMemory does not count the bytes freed, llGetFreeMemory instead counts all the bytes never yet used.
- ^ http://www.langnetsymposium.com/2009/talks/17-JimPurbrick-SecondLife.html
- ^ Due to the design of the LSO VM, a defragment function is impossible.
function integer llGetFreeMemory();