Results 1 to 3 of 3

Thread: Component doesn't destroy its own bindings created by it on a higher level viewModel

Hybrid View

Previous Post Previous Post   Next Post Next Post
    Success! Looks like we've fixed this one. According to our records the fix was applied for a bug in our system in a recent build.
  1. #1

    Default Component doesn't destroy its own bindings created by it on a higher level viewModel

    According to https://docs.sencha.com/extjs/6.0/application_architecture
    /view_models_data_binding.html
    recomendations (Dont create child ViewModels unless they are actually needed) this example should work:

    https://fiddle.sencha.com/?fiddle=ucj#fiddle/v7d

    Press the 'destroy' button

    You see how changing viewModel's property causes an undestroyed binding accessing the destroyed component's setDisabled method which throws an exception.

    There is not always so obvious exception as going in this fiddle and most of the time bindings hang in memory causing memory leaks.

    ExtJs 6.0.1.250
    All browsers

  2. #2
    Sencha Premium User
    Join Date
    Apr 2007
    Location
    Sydney, Australia
    Posts
    19,258

    Default

    Thanks for the post, this issue is already resolved in the latest nightlies and will be fixed in the next release.

  3. #3
    Ext JS Premium Member
    Join Date
    Apr 2010
    Location
    Omaha, NE
    Posts
    631

    Default

    Is there a workaround for this? This bug is causing problems all over our app where we destroy containers and updates to a parent VM cause exceptions that kill our app.

Similar Threads

  1. ViewModel bindings are affecting OTHER views!
    By marc.fearby in forum Ext 5: Q&A
    Replies: 10
    Last Post: 18 Oct 2015, 1:54 PM
  2. App not working in higher than Android API Level 10
    By rafi_ccj in forum Sencha Touch 2.x: Q&A
    Replies: 3
    Last Post: 20 Oct 2013, 9:18 PM
  3. [FIXED] DataView doesn't destroy store, created by default
    By artsiom_aliakseyenka in forum Sencha Touch 2.x: Bugs
    Replies: 1
    Last Post: 6 Dec 2012, 8:37 AM
  4. [FIXED-515] Component doesn't destroy its Scroller
    By elishnevsky in forum Sencha Touch 1.x: Bugs
    Replies: 3
    Last Post: 4 Nov 2010, 8:23 PM
  5. [Bug?] Ext.Component doesn't destroy context menus?
    By mjlecomte in forum Ext 2.x: Help & Discussion
    Replies: 8
    Last Post: 18 Dec 2008, 3:26 PM

Tags for this Thread

Posting Permissions

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