# Unable to view NR from ordinary browser window after browser crash

**URL:** <https://discourse.nodered.org/t/unable-to-view-nr-from-ordinary-browser-window-after-browser-crash/61647>\
**Category:** General\
**Created:** [22 April 2022 15:13 UTC](https://discourse.nodered.org/t/unable-to-view-nr-from-ordinary-browser-window-after-browser-crash/61647 "2022-04-22T15:13:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JayNaire](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jaynaire/32/17343_2.png) [@JayNaire](https://discourse.nodered.org/u/JayNaire)\
**Post date:** [22 April 2022 15:13 UTC](https://discourse.nodered.org/t/unable-to-view-nr-from-ordinary-browser-window-after-browser-crash/61647/1 "2022-04-22T15:13:57Z")

</div>

I can't load NR (from a local rpi server) in a Firefox standard window any more.  
It still loads fine in a Firefox Private Window or Chrome.

The error\* I'm getting suggests corruption in Firefox profiles; ( FF crashed running NR yesterday ).  
Normally, I'd just clear out NR cookies, storage etc. and expect to continue. But there aren't any NR cookies.

The unhappy file is red/red.min.js. (There was a similar error from a monaco.min file which disappeared when I changed from monaco to ace in settings.js.)

Any thoughts (or preferably quick fixes that don't involve faffing with FF!) please?

Note: NR was unaffected on the server.

\*Debugger Error:

```auto
Uncaught 
Exception { name: "NS_ERROR_STORAGE_CONSTRAINT", message: "", result: 2153971715, filename: "http://rpi4-home:2000/red/red.min.js?v=2.1.1", lineNumber: 16, columnNumber: 0, data: null, stack: "init@http://rpi4-home:2000/red/red.min.js?v=2.1.1:16:21746\ninit@http://rpi4-home:2000/red/red.min.js?v=2.1.1:16:19049\n@http://rpi4-home:2000/red/main.min.js?v=2.1.1:16:161\ne@http://rpi4-home:2000/vendor/vendor.js?v=2.1.1:2:30005\nDeferred/then/l/</t<@http://rpi4-home:2000/vendor/vendor.js?v=2.1.1:2:30307\n" }
​
columnNumber: 0
​
data: null
​
filename: "http://rpi4-home:2000/red/red.min.js?v=2.1.1"
​
lineNumber: 16
​
message: ""
​
name: "NS_ERROR_STORAGE_CONSTRAINT"
​
result: 2153971715
​
stack: "init@http://rpi4-home:2000/red/red.min.js?v=2.1.1:16:21746\ninit@http://rpi4-home:2000/red/red.min.js?v=2.1.1:16:19049\n@http://rpi4-home:2000/red/main.min.js?v=2.1.1:16:161\ne@http://rpi4-home:2000/vendor/vendor.js?v=2.1.1:2:30005\nDeferred/then/l/</t<@http://rpi4-home:2000/vendor/vendor.js?v=2.1.1:2:30307\n"
​
<prototype>: ExceptionPrototype { toString: toString(), name: Getter, message: Getter, … }
red.min.js:16

```

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [22 April 2022 15:59 UTC](https://discourse.nodered.org/t/unable-to-view-nr-from-ordinary-browser-window-after-browser-crash/61647/2 "2022-04-22T15:59:48Z")

</div>

Have you tried doing ctrl-f5 a few times to force-clear the cached javascript and css?

Also, try using an in-private session just to check that it is actually something cached in your main profile.

---

<div class="post-metadata">

**Author:** ![Steve-Mcl](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/steve-mcl/32/4826_2.png) [@Steve-Mcl](https://discourse.nodered.org/u/Steve-Mcl)\
**Post date:** [22 April 2022 18:50 UTC](https://discourse.nodered.org/t/unable-to-view-nr-from-ordinary-browser-window-after-browser-crash/61647/3 "2022-04-22T18:50:29Z")

</div>

> [@JayNaire](#):
>
> `NS_ERROR_STORAGE_CONSTRAINT`

> <https://stackoverflow.com/questions/34900350/what-causes-ns-error-storage-constraint-in-firefox>

---

<div class="post-metadata">

**Author:** ![JayNaire](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/jaynaire/32/17343_2.png) [@JayNaire](https://discourse.nodered.org/u/JayNaire)\
**Post date:** [23 April 2022 12:19 UTC](https://discourse.nodered.org/t/unable-to-view-nr-from-ordinary-browser-window-after-browser-crash/61647/4 "2022-04-23T12:19:45Z")

</div>

Thanks to @TotallyInformation & @Steve-Mcl for suggestions.

I found the only way of getting round this problem was to use a different URL to get to NR since it appears FF ties local storage permissions to the unresolved URL. So "mdns-url.local" gives you fresh local storage for monaco etc. compared with "mdns-url" without the .local. Actually fixing the original corrupt storage is too intricate.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [22 June 2022 12:19 UTC](https://discourse.nodered.org/t/unable-to-view-nr-from-ordinary-browser-window-after-browser-crash/61647/5 "2022-06-22T12:19:48Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.