Receiver-consuming calls: an abandoned receiver leaks, a substituted one is over-released

Aperta
#571 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
12/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp, javascript, objective-c
Ambito
mobile-dev

Direzione di ricerca

Start with #569 and its specs to learn the retain/release contract already established for results, then read ArgConverter::MethodCallback and Interop::ReleasesCachedOwnedReturn alongside the Caches::Instances entry to see where the receiver's reference is passed or dropped. The fixture TNSSubstitutingInit is named for a substituting initializer; use it plus AddressSanitizer specs to reproduce each of the five listed leaks before changing anything. Done means exact counts hold for every caller/implementation pair listed in the tests section.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Summary

Initializers and NS_REPLACES_RECEIVER methods (-awakeAfterUsingCoder:) consume their receiver: the caller hands over its reference, and the method returns an owned object in its place, usually the receiver itself. The runtime gets the receiver's side of that contract wrong in two ways. #569 fixed the result side and lists both of these as not fixed.

1. A JS initializer that returns something else leaks its receiver

When a JS-implemented initializer returns a different object, or nil, the object allocated for the call is never released:

const X = NSObject.extend({
  init() { return someOtherObject; }, // or: return null
});
X.new();           // the allocated receiver keeps its alloc +1
new X();           // same
X.alloc().init();  // same

In ObjC, self = other; return self; releases the original under ARC. A JS initializer has no way to, and ArgConverter::MethodCallback never releases the receiver either. It can't simply do so: when the JS initializer returns what super.init…() substituted, that super initializer already consumed the receiver, and releasing it again would free it under its wrapper. The two cases look the same from MethodCallback.

A JS -awakeAfterUsingCoder: that returns another object leaves the caller's consumed reference behind in the same way.

With the wrapper lifetime work (#559 and up), the leftover retain reads as a native owner, so the abandoned receiver's wrapper stays a strong root.

2. Consuming calls on a receiver that already existed

For a call from JS, the runtime passes the receiver without a reference for the callee to consume. That is fine while the method returns its receiver. When it doesn't:

  • The receiver is over-released. A native initializer that substitutes its receiver releases it, and the only reference there is belongs to the Caches::Instances entry. The wrapper is left pointing at an object that can be freed under it. This applies to re-initializing a wrapped object, to super.init…() inside a JS initializer, and to Proto.initX.apply(this).
  • A substitute that is already wrapped leaks a retain. Interop::ReleasesCachedOwnedReturn never releases for a consumed receiver that existed before the call, because the usual result is the receiver itself, which carries no net +1. So when the result is a different, already wrapped object, its +1 stays. The likeliest case is super.init…() inside a JS initializer returning a cached singleton.

Receivers allocated for the call (X.alloc().init…(), new X()) are not affected: there the alloc +1 is the reference the initializer consumes.

Suggested fix

  1. Before every receiver-consuming call from JS on a receiver that already existed, retain the receiver, so the callee has a reference to consume. Then every result of such a call is a real +1, whatever it is, and the cache-hit rule no longer needs its Consumed exception: release unless the result is not owned.
  2. For JS-implemented initializers, record on the call whether a consuming call was made on the receiver while the JS method ran (the super.init…() case). When the JS method returns something other than the receiver and no such call was made, release the receiver in MethodCallback.

Both parts change who owns the receiver across the JS boundary, so they need the same care as #569: exact counts for every caller and implementation, under AddressSanitizer.

Tests to add

  • A JS initializer returning another object, and one returning null, through X.new(), new X() and X.alloc().init(): the allocated receiver is freed exactly once.
  • A JS initializer returning the substitute of a super initializer: the receiver is freed exactly once and not twice (a fixture for a substituting initializer exists: TNSSubstitutingInit).
  • Re-initializing a wrapped object with a native initializer that substitutes it: the original is not freed while its wrapper is live, and the substitute's count is balanced when it is already wrapped.
  • super.init…() inside a JS initializer returning an already wrapped object: no retain is left on it.
  • A JS -awakeAfterUsingCoder: returning another object: the receiver's count is balanced.

These come from tracing the code paths for #569; the receiver leak in part 1 is also visible in that PR's specs, where the abandoned receiver is never freed.

Lingua principale
JavaScript
Stelle
154
Fork
46
Merge medio
4g 2h
PR unite (30g)
30

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NativeScript/ios

Tutte le issue di NativeScript/ios

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.