Results 1 to 2 of 2

Thread: Crash on iOS

    Thank you for reporting this bug. We will make it our priority to review this report.
  1. #1
    Sencha User
    Join Date
    Aug 2015

    Default Crash on iOS

    Touch version tested:
    • Touch 2.4.2
    Browser versions or Packager version tested against:
    • Chrome
    • Safari
    Device and OS tested against:
    • iPad 2 running iOS 9
    What theme are you using for your application:
    • Default
    • Having a complex view (a schema) containing a lot of elements seems to crash the application.
    • Schema structure is as follows: A carousel with roughly ten cards (groups), each containing a panel with a predefined header, and each of these panels containing a few fieldsets (blocks, also having a predefined header), which in turn contains 1-100 lines (custom component), each consisting of a few elements.
    • Case: A schema contains ten groups, each groups have one block, each block have 60 lines, each line having 10 elements, with all other elements this results in 600-700 elements per group.
    • All-in-all, this results in a view containing 6-7 thousand elements, which is what the attached fiddle show.
    • Note: Changing the carousel to create groups dynamically when activating a card doesn't seem to fix the problem, as after navigating around for a while still causes a crash.
    Steps to reproduce the problem:
    • Open attached fiddle.
    • Wait.
    The result that was expected:
    • Fiddle runs and is interactable.
    The result that occurs instead:
    • Fiddle opens and after some time the browser crashes.
    The url to fiddle testcase:

  2. #2
    Sencha - Sustaining Engineer tristan.lee's Avatar
    Join Date
    Mar 2015
    Central Ohio


    I am not sure that this is an issue with the framework. There's a lot of components being rendered on a device with minimal memory and a lite browser (compared to the desktop). It's hard to tell exactly why the browser is crashing. I would assume it's a memory issue.

    I expect this to perform poorly though with the amount of component being renders. Viewing this in Chrome, it takes up ~450mb of memory. The amount of DOM elements being rendered and maintained for this is going to be very taxing on browser performance.
    Tristan Lee
    Sencha Inc - Sustaining Engineer

    Having an issue? Help us help you - be detailed; provide some code; demonstrate with a fiddle (

    Embed your fiddle in your post: [FIDDLE]id[/FIDDLE]

Similar Threads

  1. Ext JS 6 app crash on iOS
    By swdev519 in forum Ext JS 6.x Q&A
    Replies: 4
    Last Post: 24 Aug 2015, 7:12 AM
  2. App crash
    By huberte in forum Sencha Cmd
    Replies: 6
    Last Post: 27 Jun 2013, 11:35 AM
  3. Img causes IE to crash
    By barryglenn in forum Ext 3.x: Bugs
    Replies: 0
    Last Post: 16 May 2011, 11:27 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts