Memory issue with slide-box and scrollable content

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?

Looking much better! My 200 KB book now takes up only approx 90MB in the iOS simulator :smile:

I still reckon this is a lot of memory to use, but whether it has anything to do with the Slide-box, I cannot say just now.

Will test on device right after dinner :smile:

Edit:
Tested on my iPad, and it’s even better. It takes up 30-35 MB and does not crash. This is a very exciting update - thanks a lot @mhartington et al :smile:

3 Likes

yay, thanks @mhartington !!

1 Like

I’m seeing similair improvements :slight_smile:

1 Like

You guys have no idea how happy I am to hear this :smile:

If there are any errors, please note them in the PR

@mhartington Will do… For your happiness, you can surely ask your colleagues at the office to record a video of you dancing on a table :slight_smile: If you share a video like that, and embed it in a post you make, we will finally have an idea of how happy that makes you ^^

~I would really enjoy such a video anyways~

(@andy maybe you could shoot the vid? just a suggestion fo course ;))

1 Like

Any news if this improved implementation of slidebox is somewhere available ? I have an memory warning with 22 elements in slidebox :frowning: My ionic version is 1.0.0-beta.13 and slidebox still loading all elements in collection.

Upgrade to beta 14! There has been some api changes though I think

1 Like

Thanks @tobbe ! I’ll try that. For everybody looking for this update: here are changes in slidebox api: https://github.com/driftyco/ionic/blob/v1.0.0-beta.14/CHANGELOG.md#breaking-changes

@tobbe I updated to version 14 (with bower update) but to be honest don’t see any changes in Slidebox behaviour. As I see in the source code the API doesn’t changed :frowning:
Geez, how should I update existing project ? I just did:

  1. I’ve changes version in bower.json to driftyco/ionic-bower#1.0.0-beta.14
  2. I’ve made bower update

I don’t understand. This is the source code of beta 14 for slidebox. It doesn’t change!

Hi which version ionic add those changes.I have the issue too,the version i used is 1.0.0-rc.5,i create a slidebox with 15 item .everytime i slide the slidebox ,i put a img in current item like this

 <ion-slide-box show-pager="true" on-slide-changed="slideChanged(index)">
          <ion-slide ng-repeat="item in data.slides"> 
                    <ion-content  >
                  <ion-scroll >
                    <img class="page-content" ng-src="{{item.url}}"  >
                  </ion-scroll>
                  </ion-content>
          </ion-slide>
        </ion-slide-box>

i find that nearly 10M memeory add in the chrome when a add a new img ,i test to ng-if the img that i have read,but the memory is not be freed.

Which version i can use those ?

Hi all,

I am also facing similar problems with ion-slide-box. I have raised a query in the forum Ionic slide-box crash on iPads

I have put sample app which shows the crash on the latest ionic version v1.0.0

In our actual product, we have to create ionic slide-boxes dynamically with 3-5 ion-slides. Each ion-slide item has either an ng-repeat or a collection-repeat or an iframe drawing a chart on canvas. Once the data set increases, the app simply crashes on rotation or when we are inside a slide-box and trying to delete the existing one and create a new one.

Such crashes are not noted on lower screen-size devices like iPhone and iPad Mini.

It looks like ionic slide-box is using a lot of memory internally and may also be trigering invalid memory access.

@mhartington Is there any fix available in nightly builds? Its extremly important for us to have a working solution now

Could you please share full codes?