Unload / Release / Remove React Native View from runtime

Question

I am creating a App that uses React Native in some part, but not all.

I have an instance of RCTRootView

Setting it to nil and removing it from the superview doesn't seem to release it.

The CPU and RAM stays high, so it seems the React app stills executing on the threads.

How can I stop it?

Thanks :)

More Info: [Bridge] Deallocating memory when popping ViewController that contains React Native component #1487 github.com/facebook/react-native/issues/1487 — Gaston Morixe
– Gaston Morixe, Commented Dec 10, 2015 at 5:52

Shashi3456643 · Accepted Answer · 2017-10-11 22:15:48Z

5

RCTBridge * bridge
[bridge invalidate];
bridge = nil;

invalidate and nil will clear all modules from jsbundle and it clears RCTRootView instances from memory . Note bridge is object of RCTBridge.

edited Oct 11, 2017 at 22:15

answered Oct 11, 2017 at 22:10

Shashi3456643

2,04118 silver badges21 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Gaston Morixe · Accepted Answer · 2015-12-19 02:23:20Z

4

You have to create your own RTCBridge separately and release it ( = nil), not only the view.

answered Dec 19, 2015 at 2:23

Gaston Morixe

8472 gold badges10 silver badges21 bronze badges

1 Comment

yura Over a year ago

I stumbled on this answer, but unfortunately my memory is still climbing every time I create new RCTRootView. I create my own RCTBridge and my own RCTRootView with it, and stick it inside some UIViewController. When UIViewController goes away, why do we have to set anything to nil? Wouldn't the stack just go away? We are not in pre-ARC days here, what am I missing?

Collectives™ on Stack Overflow

Unload / Release / Remove React Native View from runtime

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related