# Browser lock up

**URL:** <https://discourse.nodered.org/t/browser-lock-up/29697>\
**Category:** General\
**Created:** [8 July 2020 06:19 UTC](https://discourse.nodered.org/t/browser-lock-up/29697 "2020-07-08T06:19:36Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [8 July 2020 06:19 UTC](https://discourse.nodered.org/t/browser-lock-up/29697/1 "2020-07-08T06:19:36Z")

</div>

Just had by browser tab freeze when selecting nodes inside a group (1.1.0)

Other NR tabs still worked - went back to original tab (browsing my Win10 instance) and had this which I've not ever had before on NR

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/8/a/8a4dd28b1f9a78d36ee5bb338c3f56c9b29d075a.png)

Waited/refreshed/waited eventually gave up and restarted NR

All seemed to be OK again but then after editing inside the same group ( bottom one) - when I went to select another group (top one) - the first one stayed with dotted visual outline

 ![image](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/7/3/730aa0a6fca8a07c51c560d4a0a3b2478943ec5b.jpeg)  
No errors showing in console  
Going to close/reopen whole browser and see if it happens again

---

<div class="post-metadata">

**Author:** ![zenofmud](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/zenofmud/32/316_2.png) [@zenofmud](https://discourse.nodered.org/u/zenofmud)\
**Post date:** [8 July 2020 14:53 UTC](https://discourse.nodered.org/t/browser-lock-up/29697/2 "2020-07-08T14:53:49Z")

</div>

Try clearing the cache too.

---

<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:** [8 July 2020 15:15 UTC](https://discourse.nodered.org/t/browser-lock-up/29697/3 "2020-07-08T15:15:08Z")

</div>

I'm getting this tab lockup with node-red V1.1.0 (certain i didnt get it pre V1.1.0)

If tab is left open for any amount of time (cant put a number on it yet but somewhere between 10m ~ 1h) it becomes unresponsive.

Cant get into console to see any issues - only recourse is a refresh or close / re-open.

#### EDIT...

FWIW - I am not using groups FWIW

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [8 July 2020 16:01 UTC](https://discourse.nodered.org/t/browser-lock-up/29697/4 "2020-07-08T16:01:23Z")

</div>

Please try with 1.1.1 - no need for any more "me too" replies if you're on 1.1.0.

This was reported on the issue list and some potential fixes went in 1.1.1 - but as I couldn't reproduce, the fixes are somewhat speculative.

That said, the early response on the issue suggests it has had a positive effect.

> <https://github.com/node-red/node-red/issues/2631>
>
> What are the steps to reproduce?
> I often leave NodeRed open in the browser as a tab. After upgrading to 1.1.0, returning...

---

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [9 July 2020 07:52 UTC](https://discourse.nodered.org/t/browser-lock-up/29697/5 "2020-07-09T07:52:10Z")

</div>

I have seen this in 1.1.1

My observations, not fact!

My main system is on an RPi3, I use a development installation on the laptop I am surfing from.

I have a 'feeling' (not confirmed yet) that if I am doing something on the main system, leave Firefox 78.0.1 tab open, go over development system and spend some time there while developing a flow, then return to main system, the page is non responsive. If I close tab, open a new tab, all is well.

I say 'feeling', I spent years looking for patterns with faults and after this happening several times, this morning I kind of sensed that it only happened when I went to the development server. Can't say for certain I have noticed that if I leave the tab and come back to it with general browsing all is OK.

I will keep and eye on it to see if I get any other situations that cause it.

---

<div class="post-metadata">

**Author:** ![mudwalker](https://avatars.discourse-cdn.com/v4/letter/m/47e85d/32.png) [@mudwalker](https://discourse.nodered.org/u/mudwalker)\
**Post date:** [10 July 2020 05:42 UTC](https://discourse.nodered.org/t/browser-lock-up/29697/6 "2020-07-10T05:42:06Z")

</div>

Don't know if this helps...

Nothing misbehaved yesterday, but, my experience this morning

Production machine running OK  
Started Node RED on laptop

(From Web Developer Console)

_Access localhost:1880/ui, Welcome screen displays (Cache?)_  
Rendered [http://localhost:1880/ui/css/app.min.less](http://localhost:1880/ui/css/app.min.less) successfully. app.min.js:532:12831  
CSS for [http://localhost:1880/ui/css/app.min.less](http://localhost:1880/ui/css/app.min.less) generated in 216ms app.min.js:532:12831  
Less has finished. CSS generated in 216ms app.min.js:532:12831  
You are using the ngTouch module.  
AngularJS Material already has mobile click, tap, and swipe support...  
ngTouch is not supported with AngularJS Material! app.min.js:148:303  
Source map error: Error: request failed with status 404  
Resource URL: [http://localhost:1880/ui/js/app.min.js](http://localhost:1880/ui/js/app.min.js)  
Source Map URL: angular-chart.min.js.map

_CTRL-F5,_  
refresh screen

_CTRL-R_  
You are using the ngTouch module.  
AngularJS Material already has mobile click, tap, and swipe support...  
ngTouch is not supported with AngularJS Material! app.min.js:148:303  
Rendered [http://localhost:1880/ui/css/app.min.less](http://localhost:1880/ui/css/app.min.less) successfully. app.min.js:532:12831  
CSS for [http://localhost:1880/ui/css/app.min.less](http://localhost:1880/ui/css/app.min.less) generated in 311ms app.min.js:532:12831  
Less has finished. CSS generated in 311ms app.min.js:532:12831  
Source map error: Error: request failed with status 404  
Resource URL: [http://localhost:1880/ui/js/app.min.js](http://localhost:1880/ui/js/app.min.js)  
Source Map URL: angular-chart.min.js.map

_Clear Data (Cache)_  
Same messages as above

_Close tab, open new tab_  
All OK

10 Jul 06:28:21 - [info] Node-RED version: v1.1.1  
10 Jul 06:28:21 - [info] Node.js version: v12.18.2  
10 Jul 06:28:21 - [info] Linux 5.3.0-62-generic x64 LE  
10 Jul 06:28:21 - [info] Loading palette nodes  
10 Jul 06:28:22 - [info] Dashboard version 2.22.1 started at /ui  
10 Jul 06:28:22 - [warn] rpi-gpio : Raspberry Pi specific node set inactive

Dell M6700 Laptop  
Ubuntu 18.04LTS  
Firefox 78.0.1

---

<div class="post-metadata">

**Author:** ![cymplecy](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/cymplecy/32/2773_2.png) [@cymplecy](https://discourse.nodered.org/u/cymplecy)\
**Post date:** [8 September 2020 05:42 UTC](https://discourse.nodered.org/t/browser-lock-up/29697/7 "2020-09-08T05:42:16Z")

</div>

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