File: TraceWrapperReference.md

package info (click to toggle)
chromium 139.0.7258.127-1~deb13u1
  • links: PTS, VCS
  • area: main
  • in suites:
  • size: 6,122,096 kB
  • sloc: cpp: 35,100,771; ansic: 7,163,530; javascript: 4,103,002; python: 1,436,920; asm: 946,517; xml: 746,709; pascal: 187,653; perl: 88,691; sh: 88,436; objc: 79,953; sql: 51,488; cs: 44,583; fortran: 24,137; makefile: 22,147; tcl: 15,277; php: 13,980; yacc: 8,984; ruby: 7,485; awk: 3,720; lisp: 3,096; lex: 1,327; ada: 727; jsp: 228; sed: 36
file content (8 lines) | stat: -rw-r--r-- 676 bytes parent folder | download | duplicates (17) 
1
2
3
4
5
6
7
8
 
# Wrapper Tracing Reference

*Wrapper tracing is deprecated* and not in use anymore. Blink uses *unified heap* these days which just relies on regular Oilpan types for C++.

In case you are looking for how to keep JavaScript wrapper alive from C++ using tracing use the following:
- Use `Member<T>` for any managed pointer, independent of whether a JavaScript object is transitively reachable or not. With wrapper tracing interesting references required manually annotating  with `TraceWrapperMember<T>`. This is not needed anymore; in fact, the type does not exist anymore.
- Use `TraceWrapperV8Reference<T>` to annotate references to V8 that this object should keep alive.