recording halts/crashes on some pages/interactions
YoraiLevi opened this issue · 4 comments
When recording on chrome/edge(chromium) some pages halt and won't respond.
Not sure exactly why it happens but it seem to happen on pages that are ajax based rather than static.
given enough time it sometimes is able to record without crashing the page
the vertical "..." menu at https://www.youtube.com/feed/history halts the page but after a while records the action
the X for "Remove from watch history" at https://www.youtube.com/feed/history halts the page completely and is not being recorded
all this while https://www.youtube.com/ seem to be recording fine
The entire page also is very slow and clunky when using the extension
@YoraiLevi I can't reproduce this on Chrome. Please just use Chrome and not Chrome/edge as this extension is not tested on that.
This was tested on chrome and edge(chromium) as noted by the / and brackets.
Tested again it is halting the entire page on my system.
Chrome Screen recording (recorded via window's Game Bar)
Pressed start to puppeteer record(context menu doesn't show up in video)
Pressed "X" to remove video
X is being pressed constantly
trying to interact with the page by pressing on "..." and on random places/links
no response.
"X" is still being 'pressed'
Stops puppeteer recording.
(4) YouTube - Google Chrome 2020-07-03 01-39-30.zip
code generated after stopping the recording.
const puppeteer = require('puppeteer');
const browser = await puppeteer.launch({ headless: false })
const page = await browser.newPage()
await page.goto('https://www.youtube.com/feed/history')
await page.setViewport({ width: 1676, height: 833 })
await browser.close()after a while this message pops up
if ignore for a long while it disappears and the page continues with all the intended actions being performed(and if you don't pause the recording then recorded actions too).
This happen in multiple sites with similar non static button interactions.
@YoraiLevi Thanks for reproducing, I' reopening as I think I can reproduce now too. I've honestly never ever seen this behaviour before. I do not have a solution for this so a patch or analysis would be appreciated.