Memory issue with slide-box and scrollable content

The content of the book is never supposed to be updated, once it’s assigned to the slide-box. (It has a randomize feature that allows the chapters to be ordered randomly, but I’ve taken that out now, while I’m testing).

The reason why I needed to refresh the slide-box was to support the lazy-loading mechanism I made. It kept the size of the book down to just three pages: The “current”, the “previous” and the “next” page. On every page change, the pages would then be updated with the correct content.

As I recall it, the only way I could keep the pages scrollable was if I forced a refresh using the “update()” method on the slide-box delegate, and this is the one that was visible to the user (it would draw three rectangles on screen and then move them into correct positioning some milliseconds later).

Hmm I hope you can wait till @mhartington responds, (and at the same time, I hope for you he does fast ;)), because it sounds like the slide-box must have a way to update without this being visible… No experience with slide-box on this subject though at my end though.

Seems like you’ve tried everything you could so far though :slight_smile: Maybe reproduce a codepen to show the visual update, because it sounds like an issue that isn’t desired in any situation, might be just a bug in ion-slide-box

Hey guys, a bit late to the conversation.

So the slide-box updates are in the work, as well have an open PR for it

When this stuff is finished, slide-box will kick ass, and be a lot more performant. The current implementation of slide-box is a bit rough so once this one is finished, it will be a big boost and should take care of a lot of performance issues

2 Likes

Hi @mhartington, is there an expected release date (even in the nightly build)? I’m planning to launch an iOS app using slide-boxes very soon, so wondering if it’s worth waiting a few days.

Thanks

@henrik242 sound like the WIP @mhartington posted is exactly what is causing your problem (at least the current next and previous is scheduled in the WIP, including some perfromance issues). Might be worth the wait in my opinion… Not sure about deadlines etc on your side though :wink:

@mhartington any ideas on expected release like @pierre asked? Sounds like an awesome release to me :slight_smile: And I’m planning to use slide box in my project as well.

I can let you both know if a few hours, meeting time with everyone

2 Likes

@mhartington great, looking forward!

1 Like

Hi @mhartington, how did the meeting go?

This is really exciting news! Looking much forward to testing this :slight_smile:

I tried to implement exactly the same lazy-loading mecanism and faced the same issue…
Knowing that the Ionic team is working on a better slide-box, I decided to postpone my work on this…

About the memory issues, I’m curious to know if you tried to check the memory consumption in chrome (desktop) to see if it is really less…

Hi @elSolo,
I loaded the app in Google Chrome, but I’m not entirely sure about the exact memory consumption of the specific app. Google spawns a number of helpers, each taking up some memory, and the Google Chrome process itself eats up around 50 MB upon launch.

Browsing to the app increases the memory consumption of the main Chrome process as well as one or two of the helper processes. Tried to do this a couple of times, but could not really determine anything from it.

Safari spawns a Safari process as well as a Safari Web content process. They take up approx 35 MB in total. When browsing to the app, the sum is increased to around 70 MB.

This problem causes my navigation to be quite laggy. Looking forward to the update! :slight_smile:

Hey everyone, so the meeting went well. A lot of the work for the new slide-box implementation is done, it’s just the last few part that need to finished up. Expect this and a few other things to make their way into the framework before 1.0 final :wink:

1 Like

That’s great news!

Is the new slide-box likely to be part of the next beta?

How far (in terms of approximate number of weeks) are you from a final version?

/h

Can put a date on when 1.0 will be out. If something happens and we can’t make it, we don’t want to seem like liars :smile:

What I can say is that we’re working to get the beta’s finalized soon and start doing a few RC.

How far (in terms of approximate number of weeks) are we from the next beta release(with the new slide-box update)? :smiley:

Can’t really say unfortunately

Ok understood. So I guess I’ll take the assumption that we’re talking at least a number of weeks and push my app for approval at Apple and work on updating once the RC including the new slide box is available…

Thanks!

1 Like

Same problem here, my App crashes in iOS after several memory warnings.

Looking forward to the update of the slide-box!

1 Like

Alright guys…the moment is here…

Big changes to slide box in the nightly builds. Would you all be able to test it out and report any errors?