Browser lock up

[cymplecy]

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

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

No errors showing in console
Going to close/reopen whole browser and see if it happens again

[zenofmud]

Try clearing the cache too.

[Steve-Mcl]

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

[knolleary]

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.

Blank window in Chrome after returning to NR

[mudwalker]

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.

[mudwalker]

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 successfully. app.min.js:532:12831
CSS for 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
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 successfully. app.min.js:532:12831
CSS for 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
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