|Did you know ...||Search Documentation:|
The clause garbage collector (CGC) scans the environment stacks of all threads for referenced dirty predicates and at which generation this reference accesses the predicate. It then removes the references for clauses that have been retracted before the oldest access generation from the clause list as well as the secondary clauses indexes of the predicate. If the clause list is not being scanned, the clause references and ultimately the clause itself is reclaimed.
The clause garbage collector is called under three conditions, (1) after reloading a source file, (2) if the memory occupied by retracted but not yet reclaimed clauses exceeds 12.5% of the program store, or (3) if skipping dead clauses in the clause lists becomes too costly. The cost of clause garbage collection is proportional with the total size of the local stack of all threads (the scanning phase) and the number of clauses in all `dirty' predicates (the reclaiming phase).
true. Values for Status are
stop. The latter stops the
gcthread but allows is to be recreated lazily. This is use by e.g., fork/1 to avoid forking a multi-threaded application. See also gc_thread.
loop :- generator, trim_stacks, potentially_expensive_operation, stop_condition, !.
The Prolog top-level loop is written this way, reclaiming memory resources after every user query.
argument. The table below describes the Key(Value) pairs. Value can be an arithmetic integer expression. For example, to specify a 2 GB limit for the global stack, one can use:
?- set_prolog_stack(global, limit(2*10**9)).
Current settings can be retrieved with prolog_stack_property/2.
permission_erroris raised. If the limit is larger than supported, the system silently reduces the requested limit to the system limit.