Searched refs:finalizers (Results 1 – 13 of 13) sorted by relevance
| /third_party/python/Modules/ |
| D | gcmodule.c | 677 move_legacy_finalizers(PyGC_Head *unreachable, PyGC_Head *finalizers) in move_legacy_finalizers() argument
694 gc_list_move(gc, finalizers); in move_legacy_finalizers()
733 move_legacy_finalizer_reachable(PyGC_Head *finalizers) in move_legacy_finalizer_reachable() argument
736 PyGC_Head *gc = GC_NEXT(finalizers); in move_legacy_finalizer_reachable()
737 for (; gc != finalizers; gc = GC_NEXT(gc)) { in move_legacy_finalizer_reachable()
742 (void *)finalizers); in move_legacy_finalizer_reachable()
934 PyGC_Head *finalizers, PyGC_Head *old) in handle_legacy_finalizers() argument
939 PyGC_Head *gc = GC_NEXT(finalizers); in handle_legacy_finalizers()
940 for (; gc != finalizers; gc = GC_NEXT(gc)) { in handle_legacy_finalizers()
951 gc_list_merge(finalizers, old); in handle_legacy_finalizers()
[all …]
|
| D | gc_weakref.txt | 210 __del__ methods is to avoid running finalizers in an arbitrary order).
|
| /third_party/node/deps/v8/include/cppgc/ |
| D | README.md | 103 1. Invoke pre-finalizers.
105 Pre-finalizers are allowed to access any other on-heap objects, even those that may get destructed.
132 …finalizers are heavy because the thread needs to scan all pre-finalizers at each sweeping phase to…
133 Adding pre-finalizers to frequently created objects should be avoided.
|
| /third_party/python/Doc/library/ |
| D | weakref.rst | 288 program exits, it calls all remaining live finalizers for which
495 Comparing finalizers with :meth:`__del__` methods
554 The other advantage of weakref based finalizers is that they can be used to
555 register finalizers for classes where the definition is controlled by a
|
| /third_party/python/Misc/NEWS.d/ |
| D | 3.9.0a1.rst | 247 finalizers have been executed), do not block the collection of all objects
257 When cyclic garbage collection (gc) runs finalizers that resurrect
|
| D | 3.5.0a1.rst | 524 In rare cases, when running finalizers on objects in cyclic trash a bad
|
| /third_party/python/Doc/whatsnew/ |
| D | 3.9.rst | 447 (they are reachable from outside the isolated cycles after the finalizers have
|
| /third_party/python/Doc/c-api/ |
| D | typeobj.rst | 1389 Python code (due to finalizers, or weakref callbacks, associated with the
|
| /third_party/node/doc/api/ |
| D | n-api.md | 1706 for a persistent reference must be kept alive until finalizers for the
1708 for the same object, the finalizers for that object will not be
|
| /third_party/node/doc/changelogs/ |
| D | CHANGELOG_V13.md | 1363 …ode/commit/d7712213a4)] - **n-api**: keep napi\_env alive while it has finalizers (Anna Henningsen…
|
| D | CHANGELOG_V12.md | 1085 …ttps://github.com/nodejs/node/commit/ba2e341f1d)] - **n-api**: run all finalizers via SetImmediate…
3482 …ode/commit/af5c489f39)] - **n-api**: keep napi\_env alive while it has finalizers (Anna Henningsen…
|
| D | CHANGELOG_V14.md | 3061 …ttps://github.com/nodejs/node/commit/e7c64af404)] - **n-api**: run all finalizers via SetImmediate…
|
| /third_party/python/Misc/ |
| D | HISTORY | 1842 - Issue #21435: In rare cases, when running finalizers on objects in cyclic
7544 - Issue #14548: Make multiprocessing finalizers check pid before
23493 with finalizers. (The "get attribute" and "set attribute" methods
|