Hotfix: high CPU from favicon prefetch — a runaway startup loop that could pin the CPU is fixed.
Fixes
- fix Favicon prefetch no longer spins the CPU — on startup nextDash prefetches missing favicons for the default bookmarks. The loop only stopped once every bookmark had an icon, so a single bookmark whose favicon can't be fetched (dead URL, timeout, or blocked outbound — common on servers with restricted egress) kept it retrying the same failing network request without pause, pinning the CPU (observed ramping past 100% at idle in Docker). The loop now also stops when a batch makes no progress: fetchable icons are still fetched, and unfetchable ones no longer spin the loop. Added a regression test that fails if the loop doesn't terminate (
favicon_prefetch.go).