VNC won't start on selnium/standalone-chrome:123 with M1 Mac

[Mike Myat Min Han]

Hi there,

I'm using selenium/standalone-chrome:123 on orbstack with a M1 mac using the following config in my docker-compose.yml.

```

chrome-server:
    image: selenium/standalone-chrome:123.0
    ports:
      - "7900:7900"

```

When I start the container VNC would always exit with SIGTRAP and won't be available for me to use at port 7900. The log outputs "chrome-server-1  | 2024-04-01 04:52:57,791 INFO exited: vnc (terminated by SIGTRAP; not expected)"

When I try to run /opt/bin/start-novnc.sh I get the following output.

```

Trying to update the open file descriptor limit from 1048576 to 100000.
Successfully update the open file descriptor limit.
assertion failed [!mmap_result.is_error && mmap_result.value == kSlabAllocatorInterval.left]: Could not mmap data for the VMTracker slab allocator: 12
(VMAllocationTracker.cpp:318 init)
 /opt/bin/start-novnc.sh: line 30:   270 Trace/breakpoint trap   /opt/bin/noVNC/utils/novnc_proxy --listen ${NO_VNC_PORT:-$SE_NO_VNC_PORT} --vnc localhost:${VNC_PORT:-$SE_VNC_PORT}

```

Not sure what I am doing wrong here. Can anyone help?

- Mike