Você procurou por: garbage (Inglês - Kabiliano)

garbage collection
alqaḍ n iḍumman

garbage after “</”.
isefka arimeγta deffir n “</”.

garbage in “colgroup” fragment.
isefka irameγta deg uceqquf “colgroup”.

the cycle collector required a garbage collection.
aleqqaḍ n tawala isra alqaḍ n iḍuman.

retaining paths (from garbage collector roots)
iberdan n trekkabin (seg iẓuṛan n ulqaḍ n iḍumman)

there was an api call to force garbage collection.
iḍra-d usiwel n api i utellel n ulqaḍ n iḍumman.

javascript allocated too many bytes, and forced a garbage collection.
javascript iḥeṛṛ deqs n iṭṭamḍanen, u isekmer alqaḍ n iḍuman.

received an inter-process message that requested a garbage collection.
irsed izen agrakala id-isutren alqaḍ n iḍuman.

components.utils.forcegc() was called to force a garbage collection.
components.utils.forcegc() ittusawel i utellel n ulqaḍ n iduman.

firefox destroyed a javascript runtime or context, and this was the final garbage collection before shutting down.
firefox ihudd tawennaṭ neγ amnaḍ n javascript, d wa i d alqaḍ aneggaru n iḍumman send asensi.

javascript returned to the event loop, and it has been a relatively long time since firefox performed a garbage collection.
javascript returned to the event loop, and it has been a relatively long time since firefox performed a garbage collection.

javascript attempted to allocate, but there was no memory available. doing a full compacting garbage collection as an attempt to free up memory for the allocation.
javascript yeɛreḍ ad iḥeṛṛ, acu kan ulac aṭas n tkatut. askussem n ulqaḍ n iḍuman d aɛraḍ n userreḥ n tkatut n uḥeṛṛi.

a full, non-incremental garbage collection was triggered because there was a faster rate of allocations than the existing incremental garbage collection cycle could keep up with.
a full, non-incremental garbage collection was triggered because there was a faster rate of allocations than the existing incremental garbage collection cycle could keep up with.