Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome Canary processes continue after CLI ends. #837

Open
goldingdamien opened this issue Feb 5, 2024 · 0 comments
Open

Chrome Canary processes continue after CLI ends. #837

goldingdamien opened this issue Feb 5, 2024 · 0 comments

Comments

@goldingdamien
Copy link

I am using storycap through npx with very standard arguments.
Executing is loading Chrome Canary to run the tool(I see multiple processes open in task manager that run in the background.).
Once the execution is finished, the processes do not close. They also continue to use quite a lot of the CPU.
The CLI ends normally.

The only issues in the logs I can find seem to be below:

[Error: EPERM: operation not permitted, unlink 'C:\Users\[USER]\AppData\Local\Temp\puppeteer_dev_chrome_profile-NEcEAc\CrashpadMetrics-active.pma'] {
  errno: -4048,
  code: 'EPERM',
  syscall: 'unlink',
  path: 'C:\\Users\\[USER]\\AppData\\Local\\Temp\\puppeteer_dev_chrome_profile-NEcEAc\\CrashpadMetrics-active.pma'
}

One component seems to be triggering an error(Standard react.js onChange warning causing error + JSHandler@error).

Environment: Windows 11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant