-
Notifications
You must be signed in to change notification settings - Fork 9k
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
[Bug]: Chromium 109.0.5412.0 (r1069273) crashes on M1 Mac when using devtools console #9470
Comments
Able to repro but don't see any crash logs or anything like this. Note that we currently don't officially support ARM and it looks like a problem with the binary so it will be probably solved with the next binary roll. |
We also found a problem with the ARM experimental flag: it looks like the flag would lead to the x86 binary download as well. I will give it a try once the new version is published. |
AFAICT neither setting |
🤖 I have created a release *beep* *boop* --- <details><summary>puppeteer: 19.5.2</summary> ## [19.5.2](puppeteer-v19.5.1...puppeteer-v19.5.2) (2023-01-11) ### Miscellaneous Chores * **puppeteer:** Synchronize puppeteer versions ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 19.5.1 to 19.5.2 </details> <details><summary>puppeteer-core: 19.5.2</summary> ## [19.5.2](puppeteer-core-v19.5.1...puppeteer-core-v19.5.2) (2023-01-11) ### Bug Fixes * make sure browser fetcher in launchers uses configuration ([#9493](#9493)) ([df55439](df55439)), closes [#9470](#9470) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
PUPPETEER_EXPERIMENTAL_CHROMIUM_MAC_ARM is fixed in 19.5.2 but the crash still happens so #9470 (comment) still applies. |
🤖 I have created a release *beep* *boop* --- <details><summary>puppeteer: 19.6.0</summary> ## [19.6.0](puppeteer-v19.5.2...puppeteer-v19.6.0) (2023-01-23) ### Miscellaneous Chores * **puppeteer:** Synchronize puppeteer versions ### Dependencies * The following workspace dependencies were updated * dependencies * puppeteer-core bumped from 19.5.2 to 19.6.0 </details> <details><summary>puppeteer-core: 19.6.0</summary> ## [19.6.0](puppeteer-core-v19.5.2...puppeteer-core-v19.6.0) (2023-01-23) ### Features * **chromium:** roll to Chromium 110.0.5479.0 (r1083080) ([#9500](#9500)) ([06e816b](06e816b)), closes [#9470](#9470) * **page:** Adding support for referrerPolicy in `page.goto` ([#9561](#9561)) ([e3d69ec](e3d69ec)) ### Bug Fixes * firefox revision resolution should not update chrome revision ([#9507](#9507)) ([f59bbf4](f59bbf4)), closes [#9461](#9461) * improve screenshot method types ([#9529](#9529)) ([6847f88](6847f88)) </details> --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Bug description
Steps to reproduce the problem:
Expect:
Actual:
Example script:
Notes:
Puppeteer version
19.4.1
Node.js version
19.1.0
npm version
8.19.3
What operating system are you seeing the problem on?
macOS
Configuration file
No response
Relevant log output
No response
The text was updated successfully, but these errors were encountered: