Quantcast
Channel: Ember.JS - Latest topics
Viewing all articles
Browse latest Browse all 4829

Error in IE11, sometimes app won't boot up

$
0
0

@Pop_Levente wrote:

Hi Guys,

since a few weeks our automated tests (selenium browserstack interaction tests), are getting white screens in IE11, already at the login of our ember application.

the error is : [{"message":"Exception thrown and not caught","source":"https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js","lineno":19832,"colno":9,"error":{"stack":"TypeError: Can't call method on null\n at module.exports (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:1062:24)\n at module.exports (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:2595:3)\n at keys (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:4509:5)\n at initialize (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:129169:5)\n at Anonymous function (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:20914:9)\n at Vertices.prototype.each (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:37090:17)\n at Vertices.prototype.walk (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:37019:13)\n at DAG.prototype.each (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:36964:13)\n at DAG.prototype.topsort (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:36970:13)\n at _runInitializer (https://regressietest.bluedolphin-tst.valueblue.nl/assets/vendor-a83cc45fd7a1bc030160eff353a5a4bd.js:20928:7)"}}]

and checked that line and it’s at:

    if (this.autoboot) {
      var instance = void 0;

      if (this._globalsMode) {
        // If we already have the __deprecatedInstance__ lying around, boot it to
        // avoid unnecessary work
        instance = this.__deprecatedInstance__;
      } else {
        // Otherwise, build an instance and boot it. This is currently unreachable,
        // because we forced _globalsMode to === autoboot; but having this branch
        // allows us to locally toggle that flag for weeding out legacy globals mode
        // dependencies independently
        instance = this.buildInstance();
      }

      instance._bootSync();

      // TODO: App.ready() is not called when autoboot is disabled, is this correct?
      this.ready();

      instance.startRouting();
    }

    // For the asynchronous boot path
    this._bootResolver.resolve(this);

    // For the synchronous boot path
    this._booted = true;
  } catch (error) {
    // For the asynchronous boot path
    this._bootResolver.reject(error);

    // For the synchronous boot path
   throw error;
  }

does anyone have a clue what could be? This only happens occasionally, not always. for example 15 times out of our 60 tests, and not always the same test, but randomly.

Posts: 3

Participants: 3

Read full topic


Viewing all articles
Browse latest Browse all 4829

Trending Articles