Nuxt generated static site never finishes loading

Issue: Site appears to load completely but Chrome keeps spinning which blocks interaction with hyperlinks on page.

Tests : Testing the build on local env is fine but not netlify (obv very different env - but still). Running site with yarn dev in local does provide the following error You may have an infinite update loop in a component render function. This could be the issue. Netlify build does not provide any console errors or warnings.

Site: [https://epic-darwin-52bbb3.netlify.app](https://epic-darwin-52bbb3.netlify.app](https://epic-darwin-52bbb3.netlify.app](https://epic-darwin-52bbb3.netlify.app)

Site appears to be generating without errors. Full build report:

2:39:12 PM: Build ready to start
2:39:14 PM: build-image version: 3571f0130496395a23bffe9820bc78b4f73a6234
2:39:14 PM: build-image tag: v3.7.0
2:39:14 PM: buildbot version: bd229cb35229750ceaca8bc031fa7f526aef77de
2:39:14 PM: Fetching cached dependencies
2:39:14 PM: Starting to download cache of 108.1MB
2:39:16 PM: Finished downloading cache in 2.51583361s
2:39:16 PM: Starting to extract cache
2:39:21 PM: Finished extracting cache in 4.911587114s
2:39:21 PM: Finished fetching cache in 7.502149279s
2:39:21 PM: Starting to prepare the repo for build
2:39:22 PM: Preparing Git Reference refs/heads/main
2:39:24 PM: Different publish path detected, going to use the one specified in the Netlify configuration file: 'dist' versus 'dist/' in the Netlify UI
2:39:24 PM: Starting build script
2:39:24 PM: Installing dependencies
2:39:24 PM: Python version set to 2.7
2:39:25 PM: Started restoring cached node version
2:39:27 PM: Finished restoring cached node version
2:39:28 PM: v12.18.0 is already installed.
2:39:29 PM: Now using node v12.18.0 (npm v6.14.4)
2:39:29 PM: Started restoring cached build plugins
2:39:29 PM: Finished restoring cached build plugins
2:39:29 PM: Attempting ruby version 2.7.1, read from environment
2:39:31 PM: Using ruby version 2.7.1
2:39:31 PM: Using PHP version 5.6
2:39:31 PM: Started restoring cached yarn cache
2:39:31 PM: Finished restoring cached yarn cache
2:39:31 PM: Started restoring cached node modules
2:39:31 PM: Finished restoring cached node modules
2:39:32 PM: Installing NPM modules using Yarn version 1.22.4
2:39:32 PM: yarn install v1.22.4
2:39:32 PM: [1/4] Resolving packages...
2:39:33 PM: success Already up-to-date.
2:39:33 PM: Done in 0.91s.
2:39:33 PM: NPM modules installed using Yarn
2:39:33 PM: Started restoring cached go cache
2:39:33 PM: Finished restoring cached go cache
2:39:33 PM: go version go1.14.4 linux/amd64
2:39:33 PM: go version go1.14.4 linux/amd64
2:39:33 PM: Installing missing commands
2:39:33 PM: Verify run directory
2:39:35 PM: ​
2:39:35 PM: ────────────────────────────────────────────────────────────────
2:39:35 PM:   Netlify Build                                                 
2:39:35 PM: ────────────────────────────────────────────────────────────────
2:39:35 PM: ​
2:39:35 PM: ❯ Version
2:39:35 PM:   @netlify/build 9.11.0
2:39:35 PM: ​
2:39:35 PM: ❯ Flags
2:39:35 PM:   apiHost: api.netlify.com
2:39:35 PM:   cacheDir: /opt/build/cache
2:39:35 PM:   deployId: 60541ce07c490e00078b8c76
2:39:35 PM:   mode: buildbot
2:39:35 PM:   testOpts:
2:39:35 PM:     silentLingeringProcesses: ''
2:39:35 PM: ​
2:39:35 PM: ❯ Current directory
2:39:35 PM:   /opt/build/repo
2:39:35 PM: ​
2:39:35 PM: ❯ Config file
2:39:35 PM:   No config file was defined: using default values.
2:39:35 PM: ​
2:39:35 PM: ❯ Context
2:39:35 PM:   production
2:39:35 PM: ​
2:39:35 PM: ────────────────────────────────────────────────────────────────
2:39:35 PM:   1. Build command from Netlify app                             
2:39:35 PM: ────────────────────────────────────────────────────────────────
2:39:35 PM: ​
2:39:35 PM: $ yarn generate
2:39:36 PM: yarn run v1.22.4
2:39:36 PM: $ nuxt generate
2:40:03 PM: Done in 27.75s.
2:40:04 PM: ​
2:40:04 PM: (build.command completed in 28s)
2:40:04 PM: ​
2:40:04 PM: ────────────────────────────────────────────────────────────────
2:40:04 PM:   2. Deploy site                                                
2:40:04 PM: ────────────────────────────────────────────────────────────────
2:40:04 PM: ​
2:40:04 PM: Starting to deploy site from 'dist'
2:40:04 PM: Creating deploy tree 
2:40:04 PM: Creating deploy upload records
2:40:04 PM: 4 new files to upload
2:40:04 PM: 0 new functions to upload
2:40:04 PM: Site deploy was successfully initiated
2:40:04 PM: ​
2:40:04 PM: (Deploy site completed in 404ms)
2:40:04 PM: ​
2:40:04 PM: ────────────────────────────────────────────────────────────────
2:40:04 PM:   Netlify Build Complete                                        
2:40:04 PM: ────────────────────────────────────────────────────────────────
2:40:04 PM: ​
2:40:04 PM: (Netlify Build completed in 28.5s)
2:40:04 PM: Starting post processing
2:40:04 PM: Post processing - HTML
2:40:04 PM: Caching artifacts
2:40:04 PM: Started saving node modules
2:40:04 PM: Finished saving node modules
2:40:04 PM: Started saving build plugins
2:40:04 PM: Finished saving build plugins
2:40:04 PM: Started saving yarn cache
2:40:04 PM: Finished saving yarn cache
2:40:04 PM: Started saving pip cache
2:40:04 PM: Finished saving pip cache
2:40:04 PM: Started saving emacs cask dependencies
2:40:04 PM: Post processing - header rules
2:40:04 PM: Finished saving emacs cask dependencies
2:40:04 PM: Started saving maven dependencies
2:40:04 PM: Post processing - redirect rules
2:40:04 PM: Finished saving maven dependencies
2:40:04 PM: Started saving boot dependencies
2:40:04 PM: Finished saving boot dependencies
2:40:04 PM: Started saving rust rustup cache
2:40:04 PM: Post processing done
2:40:04 PM: Finished saving rust rustup cache
2:40:04 PM: Started saving go dependencies
2:40:04 PM: Finished saving go dependencies
2:40:04 PM: Build script success
2:40:05 PM: Site is live ✨
2:40:24 PM: Finished processing build request in 1m10.071059806s

howdy ! I just tried loading the site and i have to say it loaded perfectly on my version of chrome.

Is it possible you have some browser extensions that are interfering? we know from experience they can do unexpected things. Does the problem persist in an incognito window? if no, then extensions are the problem.