Am on 0.7.2 (had this problem on previous versions too)

When I open home page (or select "Nodes"), Chrome works for a while and either gives me error 404 or crashes. I can see my RAM going up to 95% (mostly Chrome climbing above 6 GB ) in Task Manager before the crash. Firefox doesn't doesn't chew up RAM as bad (maybe 2GB) but it keeps loading and loading and loading for minutes then returns 404

With the Programs tab, it shows them almost immediately but keeps loading and Chrome soaks up all the RAM again. Firefox also shows programs but keeps loading until 404 without soaking RAM the way Chrome does.

I do have lots of nodes and programs but I don't see this kind of RAM consumption with Java AC. It peaks at ~1.5 GB

Are you using HTTP or are you using HTTPS to access eisy-ui

using https://192.168.100.249/

Try HTTP://eisy.local/

So I can't do eisy.local. It doesn't resolve because I have eISY on a separate IoT subnet (VLAN), which protects devices on my main subnet from all my Internet of (Insecure) Things devices.

I tried http with IP address and, while it didn't chew through RAM and responded quite quickly, it still gave me 404 error

Problem with using http (I thought) is that I'm sending my portal userid and password in the clear and I don't really want to do that.

1 hour ago, johnnyt said:

Am on 0.7.2 (had this problem on previous versions too)

When I open home page (or select "Nodes"), Chrome works for a while and either gives me error 404 or crashes. I can see my RAM going up to 95% (mostly Chrome climbing above 6 GB ) in Task Manager before the crash. Firefox doesn't doesn't chew up RAM as bad (maybe 2GB) but it keeps loading and loading and loading for minutes then returns 404

With the Programs tab, it shows them almost immediately but keeps loading and Chrome soaks up all the RAM again. Firefox also shows programs but keeps loading until 404 without soaking RAM the way Chrome does.

I do have lots of nodes and programs but I don't see this kind of RAM consumption with Java AC. It peaks at ~1.5 GB

Please open a ticket referencing this post, and attach the result of those urls in the ticket:

http://eisy.local/rest/profiles

http://eisy.local/rest/nodes

1 hour ago, johnnyt said:

Problem with using http (I thought) is that I'm sending my portal userid and password in the clear and I don't really want to do that.

You are correct that it sends your portal creds in clear, but that stays on your network. When eisy-ui's server verify the creds against portal, it always use tls.

It's always better to use https even on your network in case something has been compromised on your network.