Problem to start the extension about nim HOT 7 CLOSED

fehler ist nicht mehr aufgetreten. fehler lag wohl auch eher mehr an chrome selbst, da er nach einem update aufgetreten ist.issue closed

from nim.

So after the workaround, you no longer experience the problem?

from nim.

Ehm no. That is why i Call it workaround. But i loose all the Settings of the developer console.

from nim.

from nim.

Further a screen recording always helps.

from nim.

OS: Microsoft Windows [Version 10.0.18362.836]
NiM: 2.4.2
Node: v10.20.1 (i think this doesnt matter, because the error is in the startup phase of nim
screencast ist not possible anymore, because after workaround the error doesnt come up.
before the workaround ther is only an empty screen after start of NiM

maybe the cause of this issue isnt NiM. Maybe it can be Chrome Dev tools
see also
eclipsesource/tabris-js#2069

the problem is, that the routine want to migrate the property 'length' from localStorage to localSetting (array) that is not writable.

    _migrateSettingsFromLocalStorage: function() 
    {
        var localSettings = ["advancedSearchConfig", "breakpoints", "consoleHistory", "domBreakpoints", "eventListenerBreakpoints", "fileSystemMapping", "lastSelectedSourcesSidebarPaneTab", "previouslyViewedFiles", "savedURLs", "watchExpressions", "workspaceExcludedFolders", "xhrBreakpoints"].keySet();
        if (!window.localStorage)
            return;
        for (var key in window.localStorage) {
            if (key in localSettings)
                continue;var value = window.localStorage[key];
            window.localStorage.removeItem(key);
            WebInspector.settings._settingsStorage[key] = value;
        }
    },
    _clearBreakpointsWhenTooMany: function(breakpointsSetting, maxBreakpointsCount) 
    {
        if (breakpointsSetting.get().length > maxBreakpointsCount)
            breakpointsSetting.set([]);
    }
}

from nim.

This certainly does not seem like a NiM issue based solely on the stack trace. Also want to bring out this current Chromium bug: https://blog.june07.com/chromium-bug-900945/ which sounded somewhat similar in nature.

from nim.