I have a simple web application that used a timer that triggered every second (dragged onto the page that a user would navigate to after logging in).
4 weeks after deployment we saw our app was so slow it could barely load.
After checking the apache logs there were chrome 75 and chrome 77 browsers still triggering a UUID.action every second even after we replaced our app to a version without a client side timer.
The clients should have been disconnected because we're on 2015r4 that should show "Application has gone offline" when we shut down the app. I'm not sure how Chrome kept doing this.
We moved the timer into the session object to prevent this from happening in the future.
Is this a chrome problem?