I know this is by-design behavior, I’m just wondering about the limits of the { provide: RouteReuseStrategy, useClass: IonicRouteStrategy } and angular router’s leaving the entire history of DOM objects in the ion-router-outlet so the back button has DOM to animate with.
I’ve designed something that allows traversing in a way that could generate a DOM history of thousands of whole pages in a typical case. That’s gotta be a lot of DOM memory for the browser to deal with, no? Worse still, those pages are still subscribed to observers, meaning my observables can have hundreds of subscribers to update all the time!
It purges fine when I navigate back to the home page. It works fine on a beefy dev machine. Question is, does it stress test well on meeker devices? Does it include a way of bailing the hidden DOM in a low-memory situation (rather than bailing out of the whole app!) or is that something I should do myself, perhaps by forcibly interjecting a home page visit in the middle of a long history piling up?
Yes I know about { replaceUrl: true } that doesn’t avoid this and I do want at least some back functionality (perhaps 20 animated back’s) preserved, I just want this capped so we don’t get a memory crisis. Thoughts?
1 post - 1 participant