bug: ionicSlideBox resize crashes on iOS

[forrestjt]

Type: bug

Platform: ios 7 webview

Using 1.0.0-beta.10 Hafnium Heron
A call to $ionicSlideBoxDelegate.update() causes a hybrid iOS 7 app to crash with lar(Error logs reveals something about a Memory error) which is not reproducible in android or desktop. the update is being called in this context:

$scope.$on('Resize', function() {

    // This $scope.width and $scope.height are bound to each slide's width and height
$scope.width = (window.innerWidth || document.body.clientWidth);
$scope.height = (window.innerHeight || document.body.clientHeight) - document.querySelector("#navbar").clientHeight - document.querySelector("#footerbar").clientHeight;

// Need $timeout to break out of current $apply
$timeout(function() {
$ionicSlideBoxDelegate.$getByHandle('slideBoxHandle').update();
        }, 10);
    });

The crash only happens when the slidebox has a substantial size (16 ion-slides were in the test case but possibly less), and each slide contained a full-sized highchart (http://www.highcharts.com/) when the crash occurred.

[mhartington]

So we're working on revamping slide-box to be more performant. But from the sound of your situation, what you could do is hide/remove the slides that aren't either the previous, current, or next slide.

http://codepen.io/mhartington/pen/kFhAp

[forrestjt]

This is a good workaround, but unfortunately in my case It is costly to re-render each slide. I will have to just have to refresh on resize.

[mhartington]

It's actually pretty performant, since it removes the excess slides content after it leaves that threshold. But in any case, the slide box is getting some work done.

[forrestjt]

Oh I didn't mean in raw performance terms, its just that I have a group of custom directives each rendering some data pulled from the network, so re-creating them is costly in that its data would need to be reloaded. Any thoughts on whether using css visibility rather than ngIf would be sufficient?

[mhartington]

Hmm, not too sure. You can try ng-show instead and see if it works. The use case I had when I came up with this was more images so the less in the dom, the better.