Browser crashes when browser notifications are enabled and OpenNMS gets unreachable
Description
When you have browser notifications enabled and the OpenNMS instance is unreachable or stopped, the CPU usage goes to 100% and the browser can't be used anymore. You have to wait until OpenNMS is restarted and then restart the browser instance.
Still can't reproduce with this extreme effect. But I can see some leaking websocket conenctions on chromium. : Can you give it a try with the branch `jira/NMS-10567`?
Tried Chrome today running on OSX 10.14.3 with the same issue. Here is what I did:
1. Start Horizon 2. Start Chrome and Login, I've clicked Yes on Browser notification popup. I use just this one tab, I had notifications in my config globally turned on 3. Leave the start page open 4. Stop Horizon 5. Leave everything as it is and just wait 2-5 minutes you will see Chrome going over 100%, Chrome can't be used anymore and needs to be killed hardly
This is how Chrome looks like when it is not responding anymore:
When you have browser notifications enabled and the OpenNMS instance is unreachable or stopped, the CPU usage goes to 100% and the browser can't be used anymore. You have to wait until OpenNMS is restarted and then restart the browser instance.