archiveweb.page icon indicating copy to clipboard operation
archiveweb.page copied to clipboard

Archive of Instagram causes Chrome to crash on replay 💥

Open edsu opened this issue 2 years ago • 4 comments

I created an archive of https://www.instagram.com/berniesanders/ while logged into Instagram, and not using autopilot. The page seemed to archive fine but when I went to replay it crashed Chrome!

You can find the WACZ file at https://edsu-webarchives.s3.amazonaws.com/tmp/bernie.wacz

It does seem to replay in ReplayWeb.Page though (Chrome & Firefox):

https://replayweb.page/?source=https%3A%2F%2Fedsu-webarchives.s3.amazonaws.com%2Ftmp%2Fbernie.wacz#view=pages

edsu avatar Nov 07 '23 03:11 edsu

Hi, having the same issue when I'm archiving Facebok Reel step to reproduce : goto https://www.facebook.com/reel/182489734945066 archive the page successful (extension v0.11.3), not using autopilot click on 'browse archive' and then click on the latest archive to play, chrome crashed I tried to download the wacz and replay it (https://replayweb.page/ -> choose file -> choose this wacz file from my computer) and I got an error, attached screenshot chrome version 120.0.6099.109 image

rikifrank avatar Dec 26 '23 09:12 rikifrank

@ikreymer replayweb.page-1703597409385.log Attaching the console log when trying to replay on the replayweb page From logs I think it enters some recursion on the redirect , not sure if it's facebook code or replay code. Some checks I did:

  • checked earlier extension versions (reached 0.9.8) and it still happens so it's not a regression in the code.
  • FaceBook Reels are not working on previous chrome version , so I wasn't able to check if it's chrome issue My suspect that something in the site recording causes some infinite loop which crashes the replay page and then chrome (Usually chrome detects recursion , but I think replay is low level chrome may not be able to get it)

One last update: Checking https://www.instagram.com/berniesanders/ on chromium Version 110.0.5481.0 (Developer Build) (64-bit) (With latest extension) The page loads and plays o.k. on the extension so I believe the issue is one of latest chrome versions , perhaps some optimization on the V8 or in chromium itself

I encourage you all to report the crashes to chrome using: chrome://crashes/ and send the crashes from there

tsemachh avatar Dec 26 '23 13:12 tsemachh

Chrome still crashes in attemp to replay Facebook, for example from this seed: https://www.facebook.com/hashtag/nordicwaste Chrome: Version 124.0.6367.119 (Officiel version) (64-bit) (Chrome also crashes with Instagram)

SB-JM avatar May 06 '24 11:05 SB-JM

This page seems to crash Chrome when replaying in ArchiveWebPage (but not ReplayWebPage):

https://majles.alukah.net/showthread.php?t=184791

edsu avatar May 23 '24 15:05 edsu

I think I've found the issue, and it appears to be something totally random! A particular header (that appears to be used by Facebook and Instagram) is causing the browser to crash when used in the extension. The header is: origin-agent-cluster: ?0 and deals with origin isolation in the browser, not anything used by the page.

Will have a fix shortly which removes / prefixes this header as part of the usual header rewriting:

I've reported this issue here with a very simple repro: https://issues.chromium.org/issues/351564775

ikreymer avatar Jul 07 '24 20:07 ikreymer

Fixed in 0.12.4!

ikreymer avatar Jul 08 '24 01:07 ikreymer

@ikreymer indeed there is no crash anymore but I am still unable to replay this post and still get this error:

image

Our goal is to succesfuly record reels, from Instagram, Facebook or Youtube

philjoseph avatar Aug 01 '24 14:08 philjoseph