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

Unable to load some pages(GPU crash) #246

Open
itziklavon opened this issue Mar 23, 2024 · 0 comments
Open

Unable to load some pages(GPU crash) #246

itziklavon opened this issue Mar 23, 2024 · 0 comments
Labels

Comments

@itziklavon
Copy link

itziklavon commented Mar 23, 2024

Getting the following error when trying to launch some pages
Describe the bug
2024-03-23 17:43:46 DevTools listening on ws://0.0.0.0:9222/devtools/browser/2964422e-e307-4b35-8626-825ce560f5c2 2024-03-23 17:43:46 [0323/154346.222065:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable. 2024-03-23 17:43:46 [0323/154346.227906:WARNING:sandbox_linux.cc(418)] InitializeSandbox() called with multiple threads in process gpu-process. 2024-03-23 17:43:46 [0323/154346.251646:WARNING:dns_config_service_linux.cc(428)] Failed to read DnsConfig. 2024-03-23 17:43:59 [0323/154359.060333:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory 2024-03-23 17:43:59 [0323/154359.060436:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory 2024-03-23 17:43:59 [0323/154359.060575:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory 2024-03-23 17:43:59 [0323/154359.060585:WARNING:property.cc(144)] DaemonVersion: GetAndBlock: failed. 2024-03-23 17:43:59 [0323/154359.060622:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory 2024-03-23 17:43:59 [0323/154359.060644:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory 2024-03-23 17:44:01 [0323/154401.427045:ERROR:validation_errors.cc(117)] Invalid message: VALIDATION_ERROR_DESERIALIZATION_FAILED 2024-03-23 17:44:01 [0323/154401.427094:ERROR:interface_endpoint_client.cc(707)] Message 1093617590 rejected by interface viz.mojom.CopyOutputResultSender 2024-03-23 17:44:01 [0323/154401.427127:ERROR:browser_child_process_host_impl.cc(759)] Terminating child process for bad message: Received bad user message: Validation failed for viz.mojom.CopyOutputResultSender.0 [VALIDATION_ERROR_DESERIALIZATION_FAILED] 2024-03-23 17:44:01 [0323/154401.430889:ERROR:gpu_process_host.cc(989)] GPU process exited unexpectedly: exit_code=9 2024-03-23 17:44:01 [0323/154401.430897:WARNING:gpu_process_host.cc(1360)] The GPU process has crashed 1 time(s) 2024-03-23 17:44:01 [0323/154401.443273:WARNING:sandbox_linux.cc(418)] InitializeSandbox() called with multiple threads in process gpu-process. 2024-03-23 17:44:01 [0323/154401.444727:WARNING:gpu_process_host.cc(1011)] Reinitialized the GPU process after a crash. The reported initialization time was 11 ms

it is happening when i open some of the pages(it is internal page so i cannot share)

If applicable, add logs to help explain your problem.

Versions
MacOS
Ddocker
Client:
Cloud integration: v1.0.35+desktop.11
Version: 25.0.3
API version: 1.44
Go version: go1.21.6
Git commit: 4debf41
Built: Tue Feb 6 21:13:26 2024
OS/Arch: darwin/arm64
Context: desktop-linux

Server: Docker Desktop 4.28.0 (139021)
Engine:
Version: 25.0.3
API version: 1.44 (minimum version 1.24)
Go version: go1.21.6
Git commit: f417435
Built: Tue Feb 6 21:14:22 2024
OS/Arch: linux/arm64
Experimental: false
containerd:
Version: 1.6.28
GitCommit: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
runc:
Version: 1.1.12
GitCommit: v1.1.12-0-g51d5e94
docker-init:
Version: 0.19.0
GitCommit: de40ad0 |

when launching some pages it works as expected, but on some, it does not
errors i see in logs relate to GPU/WEB GL

when launching the same page with browserless chrome image, it works as expected
but this image uses a lot more resources

@itziklavon itziklavon added the bug label Mar 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant