Skip to content

Running Chrome under amd64 emulation (M1) results in crashes #5766

@Niek

Description

@Niek

Any amd64 container with Chrome crashes on arm64 hosts (M1 architecture). Here is a quick sample:

docker run --rm -p 3000:3000 --platform linux/amd64 -e "PREBOOT_CHROME=true" browserless/chrome

The stderr of Chrome is:

qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[2779:2779:0618/071644.009222:ERROR:nacl_fork_delegate_linux.cc(329)] Bad NaCl helper startup ack (0 bytes)
qemu: uncaught target signal 5 (Trace/breakpoint trap) - core dumped
[2737:2787:0618/071644.207029:ERROR:file_path_watcher_linux.cc(326)] inotify_init() failed: Function not implemented (38)
[0618/071646.632623:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Function not implemented (38)
qemu: uncaught target signal 11 (Segmentation fault) - core dumped
[0618/071646.653015:ERROR:crashpad_client_linux.cc(461)] sigaltstack: Invalid argument (22)
Segmentation fault
[0618/071646.653862:ERROR:crashpad_client_linux.cc(461)] sigaltstack: Invalid argument (22)
[0618/071646.662575:ERROR:crashpad_client_linux.cc(461)] sigaltstack: Invalid argument (22)

This qemu issue seems to be related: https://gitlab.com/qemu-project/qemu/-/issues/324

Related issue: #5168
Another related issue: #5321

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions