Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>you can put a 'STAT function within one of your loops to try and figure out if and where a memory leak is occuring.</p> <p>out of memory errors usually occur in one of these situations or something similar:</p> <ul> <li><p>appending to a series which is not cleared or copied at the start of a function with a loop</p></li> <li><p>a complete tree of data is not reset to none (at each leaf and branch) in a situation where some (a single?) sub elements are referenced outside the tree and the whole data block ends up being caught in the ram unable to free itself</p></li> <li><p>when printing a very large string or nested tree of large objects (for example a VID face contains a reference to the complete styleshet, so printing the window of a big app usually fails.).</p></li> <li><p>some stack overflows (endless recursions or loops) are sometimes incorrectly reported as memory errors.</p></li> <li><p>allocation of a single item grows exponentially... like image! allocation when multiplying each pass by 10 on both axes... effectively increasing two orders of magnitude which usually fails at numbers in the n*10k range. </p></li> <li><p>the largest item in the GC sometimes never deallocates as per the suboptimal R2 GC (large images <em>may</em> have this symptom).</p></li> <li><p>recursive parse rules are creating data and a single rule is infinite (it happens very rapidly on rules like [ rule | none ] . none effectively equivalent to forever in this case.</p></li> </ul>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload