Angular RxJs Timer paused on IE11

I have a timer that periodically pumps data to the main page of my Angular4 app. For Chrome everything works fine. However, IE11 sometimes gets into a mode where Observable and in fact even Observables that are not on the timer (on other pages) will pump out old data. While Chrome is doing well with new data, IE is stuck with the numbers it had from a certain period of time in the past. When I navigate to other pages, everything is stuck in the past, so all data is consistent (but outdated).

Reloading the browser does not affect, moving to different pages does not. The only way to get Observables to start fetching new data again (without closing and restarting the browser) is to open development tools, go to the webpage, and start monitoring the network. Then he seems to lean back.

Is anyone else experiencing this or knows what might be causing it?

Additional Information.

I notice that if I leave the developer tools open for IE, I get this error after a while from a link called webpack /// webpack bootstrapxxxxxxxxxx (where x are some numbers in hex). Stopping point:

// The require function
function __webpack_require__(moduleId) {

    // Check if module is in cache
    if(installedModules[moduleId])
        return installedModules[moduleId].exports;

    // Create a new module (and put it into the cache)
    var module = installedModules[moduleId] = {
        i: moduleId,
        l: false,
        exports: {}
    };

    // Execute the module function
    modules[moduleId].call(module.exports, module, module.exports, __webpack_require__);

    // Flag the module as loaded
    module.l = true;

    // Return the exports of the module
    return module.exports;
}

      

With this error in the section "modules [moduleId] .call ...

Unable to get property 'call' of undefined or null reference

      

+1


source to share





All Articles