Gautam Kumar eb683ddd2c fix: continue rendering when Chrome hits 'Object reference chain is too long' ...

When a page's JavaScript builds deeply nested object graphs, Chrome's
DevTools Protocol returns error -32000 'Object reference chain is too
long' during WaitLoad. The page has still loaded its HTML — the error is
about Chrome's internal object tracking, not the document itself.

This change detects this specific error and proceeds with rendering
instead of failing the entire page, so sites with complex JS still get
cloned successfully (issue #36).

Signed-off-by: Gautam Kumar <gautamkumarofficial@users.noreply.github.com>

2026-06-17 08:27:21 +05:30

..

pool_test.go

Stop Chrome downloading files a crawl links to

2026-06-16 09:41:43 +07:00

pool.go

fix: continue rendering when Chrome hits 'Object reference chain is too long'

2026-06-17 08:27:21 +05:30