Comments (16)
Hm, not sure, nothing particularly stands out, but perhaps do not run in the --single-process
mode and try with --disable-gpu
? maybe some graphics dependencies are required now?
from puppeteer.
Thank you for your help, the culprit was --single-process
, as far as I know, --single-process
was mandatory on AWS Lambda Images.
I haven't tested this on other distro but if single process is an issue on the recent chrome build then where shall I post this information? It would be useful for lot of people.
from puppeteer.
This issue has an invalid Node.js version: 20
. Versions must follow SemVer formatting. Please update the form with a valid version.
from puppeteer.
Consider using the official Docker image we provide (it is not based on Alpine though and uses Chrome for Testing) https://github.com/puppeteer/puppeteer/pkgs/container/puppeteer Note that Alpine Chromium builds are not maintained by us, so please consider reaching out to the build maintainer or filing an issue for Chromium at crbug.com.
from puppeteer.
Same issue with
- [email protected] (available in docker image node:lts-alpine3.19)
- [email protected]
from puppeteer.
Try using dumpio: true to see logs from chromium. Perhaps something is missing in the Alpine image for this version.
from puppeteer.
@OrKoN I can confirm that the issue isn't with alpine, it is failing with https://github.com/puppeteer/puppeteer/pkgs/container/puppeteer image as well. I am getting same error.
Puppeteer is not connecting to latest chrome version.
Here is the sample repo,
https://github.com/ackava/puppeteer-failing-123
from puppeteer.
Try using dumpio: true to see logs from chromium. Perhaps something is missing in the Alpine image for this version.
Recurring log messages are:
[488:614:0402/093043.145357:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[488:614:0402/093043.145370:ERROR:gpu_channel_manager.cc(957)] Failed to create GLES3 context, fallback to GLES2.
[488:614:0402/093043.145378:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
[488:614:0402/093043.145391:ERROR:gpu_channel_manager.cc(968)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[488:614:0402/093043.145397:ERROR:shared_image_stub.cc(728)] SharedImageStub: unable to create context
[488:614:0402/093043.145405:ERROR:gpu_channel.cc(767)] GpuChannel: Failed to create SharedImageStub
[488:614:0402/093043.145573:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
from puppeteer.
@ackava you should not use the channel as it will pick-up with wrong binary: instead you shoud let Puppeteer to launch the bundled instance.
from puppeteer.
@OrKoN I changed index.js
to use bundled google-chrome-stable
.
Here is the error..
2024-04-02 15:15:15 [45:144:0402/094515.283495:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2024-04-02 15:15:15 [45:144:0402/094515.283711:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2024-04-02 15:15:15 [45:144:0402/094515.283751:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
2024-04-02 15:15:15 [45:144:0402/094515.283770:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
from puppeteer.
the stable is not the bundled version (Puppeteer bundles Chrome for Testing version as per https://pptr.dev/chromium-support), it is installed there to make sure all chrome dependencies are installed as well.
The following works for me:
FROM ghcr.io/puppeteer/puppeteer:22.6.2
COPY index.mjs .
ENTRYPOINT [ "node", "index.mjs" ]
import puppeteer from "puppeteer";
const p = await puppeteer.launch();
const page = await p.newPage();
console.log(await p.version())
await page.setContent(`<div><span>A</span></div>`);
await page.screenshot({
path: "a.png"
});
await p.close();
Outputs Chrome/123.0.6312.86
.
from puppeteer.
The command docker run --init --rm -it localhost/pptr:latest
(note the --init flag, it might be important). Could you please try this out and let me know if it works for you?
from puppeteer.
@OrKoN Yes I was able to get working with your example, but same on alpine doesn't work.
Does Following log indicate that dbus
is now mandetory for puppeteer? Because the official puppeteer troubleshooting for alpine doesn't mention this.
2024-04-02 15:44:54 [31:46:0402/101454.945658: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-04-02 15:44:54 [31:49:0402/101454.947206: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-04-02 15:44:54 [31:49:0402/101454.947294: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-04-02 15:44:54 [31:46:0402/101454.950821:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 15:44:54 [31:46:0402/101454.950900:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 15:44:54 [31:46:0402/101454.950915:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 15:44:54 [31:46:0402/101454.950925:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
from puppeteer.
@ackava as far as I know it is not required and those errors are warnings. We do configure dbus in our image though to suppress them. Note that for https://pptr.dev/troubleshooting we rely largely on community contributors since we cannot test all configurations by ourselves. Could you try to configure dbus and update the guide if that helps?
from puppeteer.
@OrKoN dbus errors show up even in your example so I believe dbus isn't the issue. I have collected following log and can you identify if anything is missing in configuration?
2024-04-02 22:24:01 [30:46:0402/165401.028711: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-04-02 22:24:01 [30:49:0402/165401.034760: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-04-02 22:24:01 [30:49:0402/165401.034955: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-04-02 22:24:01 [30:46:0402/165401.043442:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 22:24:01 [30:46:0402/165401.043828:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 22:24:01 [30:46:0402/165401.043881:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 22:24:01 [30:46:0402/165401.044058:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 22:24:01 [30:30:0402/165401.086290:ERROR:system_network_context_manager.cc(883)] Cannot use V8 Proxy resolver in single process mode.
2024-04-02 22:24:01 [30:30:0402/165401.087874:ERROR:policy_logger.cc(157)] :components/enterprise/browser/controller/chrome_browser_cloud_management_controller.cc(161) Cloud management controller initialization aborted as CBCM is not enabled. Please use the `--enable-chrome-browser-cloud-management` command line flag to enable it if you are not using the official Google Chrome build.
2024-04-02 22:24:01 [30:53:0402/165401.087909:ERROR:angle_platform_impl.cc(44)] RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_surface
2024-04-02 22:24:01 ERR: RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_surface
2024-04-02 22:24:01 [30:53:0402/165401.087972:ERROR:angle_platform_impl.cc(44)] RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_xcb_surface
2024-04-02 22:24:01 ERR: RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_xcb_surface
2024-04-02 22:24:01 [30:53:0402/165401.088310:ERROR:angle_platform_impl.cc(44)] Display.cpp:1070 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, enableInstanceExtensions:1715.
2024-04-02 22:24:01 ERR: Display.cpp:1070 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, enableInstanceExtensions:1715.
2024-04-02 22:24:01 [30:53:0402/165401.088487:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, enableInstanceExtensions:1715.
2024-04-02 22:24:01 [30:53:0402/165401.088521:ERROR:gl_display.cc(786)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
2024-04-02 22:24:01 [30:53:0402/165401.088554:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
2024-04-02 22:24:01 [30:53:0402/165401.088585:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
2024-04-02 22:24:01 [30:53:0402/165401.092645:ERROR:angle_platform_impl.cc(44)] RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_surface
2024-04-02 22:24:01 ERR: RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_surface
2024-04-02 22:24:01 [30:53:0402/165401.092759:ERROR:angle_platform_impl.cc(44)] RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_xcb_surface
2024-04-02 22:24:01 ERR: RendererVk.cpp:203 (VerifyExtensionsPresent): Extension not supported: VK_KHR_xcb_surface
2024-04-02 22:24:01 [30:53:0402/165401.092822:ERROR:angle_platform_impl.cc(44)] Display.cpp:1070 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, enableInstanceExtensions:1715.
2024-04-02 22:24:01 ERR: Display.cpp:1070 (initialize): ANGLE Display::initialize error 0: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, enableInstanceExtensions:1715.
2024-04-02 22:24:01 [30:53:0402/165401.092871:ERROR:gl_display.cc(515)] EGL Driver message (Critical) eglInitialize: Internal Vulkan error (-7): A requested extension is not supported, in ../../third_party/angle/src/libANGLE/renderer/vulkan/RendererVk.cpp, enableInstanceExtensions:1715.
2024-04-02 22:24:01 [30:53:0402/165401.092950:ERROR:gl_display.cc(786)] eglInitialize SwANGLE failed with error EGL_NOT_INITIALIZED
2024-04-02 22:24:01 [30:53:0402/165401.093013:ERROR:gl_display.cc(820)] Initialization of all EGL display types failed.
2024-04-02 22:24:01 [30:53:0402/165401.093041:ERROR:gl_ozone_egl.cc(26)] GLDisplayEGL::Initialize failed.
2024-04-02 22:24:01 [30:46:0402/165401.133192:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 22:24:01 [30:46:0402/165401.133296:ERROR:bus.cc(407)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
2024-04-02 22:24:01 [30:30:0402/165401.135881:ERROR:system_network_context_manager.cc(883)] Cannot use V8 Proxy resolver in single process mode.
2024-04-02 22:24:01 [30:30:0402/165401.160246:ERROR:system_network_context_manager.cc(883)] Cannot use V8 Proxy resolver in single process mode.
2024-04-02 22:24:01
2024-04-02 22:24:01 DevTools listening on ws://127.0.0.1:44063/devtools/browser/cff6671d-df71-4fdf-88be-07c8dd9533a4
2024-04-02 22:24:01 [30:73:0402/165401.952807: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-04-02 22:24:01 [30:73:0402/165401.952967: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-04-02 22:24:01 [30:73:0402/165401.953459: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-04-02 22:24:01 [30:73:0402/165401.953591: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-04-02 22:24:01 [30:73:0402/165401.953699: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-04-02 22:24:02 [0402/165402.077263:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.077964:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.078376:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.078896:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.090985:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.091392:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.092000:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.092518:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.092763:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.093094:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.093522:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.093838:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.094307:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.098551:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.109946:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.110302:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.110570:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.110915:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.111254:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.111494:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.111723:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.111984:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.112211:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.112491:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.122055:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.122539:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.122827:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.123081:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.141891:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.142318:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.142650:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.147506:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.147840:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.148523:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.148899:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.149171:WARNING:process_reader_linux.cc(95)] sched_getscheduler: Function not implemented (38)
2024-04-02 22:24:02 [0402/165402.155827:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
2024-04-02 22:24:02 [0402/165402.155909:ERROR:file_io_posix.cc(145)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)
2024-04-02 22:24:02 [30:53:0402/165402.024118:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.204246:ERROR:gpu_channel_manager.cc(957)] Failed to create GLES3 context, fallback to GLES2.
2024-04-02 22:24:02 [30:53:0402/165402.204282:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.204319:ERROR:gpu_channel_manager.cc(968)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
2024-04-02 22:24:02 [30:53:0402/165402.204344:ERROR:shared_image_stub.cc(728)] SharedImageStub: unable to create context
2024-04-02 22:24:02 [30:53:0402/165402.204440:ERROR:gpu_channel.cc(767)] GpuChannel: Failed to create SharedImageStub
2024-04-02 22:24:02 [30:53:0402/165402.204631:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.204670:ERROR:gpu_channel_manager.cc(957)] Failed to create GLES3 context, fallback to GLES2.
2024-04-02 22:24:02 [30:53:0402/165402.204691:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.204720:ERROR:gpu_channel_manager.cc(968)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
2024-04-02 22:24:02 [30:53:0402/165402.204740:ERROR:shared_image_stub.cc(728)] SharedImageStub: unable to create context
2024-04-02 22:24:02 [30:53:0402/165402.204766:ERROR:gpu_channel.cc(767)] GpuChannel: Failed to create SharedImageStub
2024-04-02 22:24:02 [30:53:0402/165402.221064:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.221123:ERROR:gpu_channel_manager.cc(957)] Failed to create GLES3 context, fallback to GLES2.
2024-04-02 22:24:02 [30:53:0402/165402.221148:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.221189:ERROR:gpu_channel_manager.cc(968)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
2024-04-02 22:24:02 [30:53:0402/165402.221214:ERROR:shared_image_stub.cc(728)] SharedImageStub: unable to create context
2024-04-02 22:24:02 [30:53:0402/165402.221247:ERROR:gpu_channel.cc(767)] GpuChannel: Failed to create SharedImageStub
2024-04-02 22:24:02 [30:53:0402/165402.221391:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.221706:ERROR:gpu_channel_manager.cc(957)] Failed to create GLES3 context, fallback to GLES2.
2024-04-02 22:24:02 [30:53:0402/165402.221735:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.221776:ERROR:gpu_channel_manager.cc(968)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
2024-04-02 22:24:02 [30:53:0402/165402.221789:ERROR:shared_image_stub.cc(728)] SharedImageStub: unable to create context
2024-04-02 22:24:02 [30:53:0402/165402.221805:ERROR:gpu_channel.cc(767)] GpuChannel: Failed to create SharedImageStub
2024-04-02 22:24:02 [30:53:0402/165402.222063:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.222106:ERROR:gpu_channel_manager.cc(957)] Failed to create GLES3 context, fallback to GLES2.
2024-04-02 22:24:02 [30:53:0402/165402.222130:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.222168:ERROR:gpu_channel_manager.cc(968)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
2024-04-02 22:24:02 [30:53:0402/165402.222195:ERROR:shared_image_stub.cc(728)] SharedImageStub: unable to create context
2024-04-02 22:24:02 [30:53:0402/165402.222219:ERROR:gpu_channel.cc(767)] GpuChannel: Failed to create SharedImageStub
2024-04-02 22:24:02 [30:53:0402/165402.240529:ERROR:check.cc(365)] Check failed: false. NOTREACHED log messages are omitted in official builds. Sorry!
2024-04-02 22:24:02 [30:53:0402/165402.240593:ERROR:gpu_channel_manager.cc(957)] Failed to create GLES3 context, fallback to GLES2.
from puppeteer.
@ackava do you know where the --single-process
flag was recommended? I don't think we recommend it in Puppeteer docs. If you could open a PR to update https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md#running-on-alpine with a note about it it, it would be great.
from puppeteer.
Related Issues (20)
- [Feature]: `Mouse.dragAndDrop` API not supported for WebDriver BiDi HOT 7
- Error: Attempted to use detached Frame HOT 15
- [Bug]: spawn ENAMETOOLONG HOT 8
- [Bug]: element disappears when cross the bound of the PDF footer HOT 5
- [Bug] puppeteer.launch with cmd file cause spawn EINVAL with recent node security patch HOT 7
- [Bug]: emoji font not displayed (just blank spaces) HOT 42
- [Bug]: `PerformanceNavigationTiming.type` is `navigation` after pressing back button HOT 7
- [Bug]: Error: net::ERR_FAILED HOT 2
- [Feature]: Let docker/Dockerfile use node:20-slim as the base image HOT 2
- [Bug]: #<NoSuchFrameException> occurs even when manually navigating to a page while the browser is idle in puppeteer HOT 2
- [Bug]: Error: Could not find Chrome (ver. 124.0.6367.78). HOT 2
- [Bug]: Instructions can be improved/corrected HOT 2
- Switch to macos-latest (arm64) in ci
- [Feature]: Request Initiator Chain HOT 8
- [Bug]: Could not find Chrome (ver. ${this.puppeteer.browserRevision}) on Docker HOT 7
- [Bug]: 'page.waitForTimeout' not working in Puppeteer 22.7.1 HOT 2
- [Bug]: use manifest V3 .When the file(manifest.json) carries ”content_scripts“,puppeteer.launch timeout HOT 17
- "[network.spec] network Request.resourceType should work for document type" is flaky in firefox
- ignoreHttpsErrors should be renamed to acceptInsecureCerts
- [Bug]: Redirect stops before the final destination that has an error Name Not Resolved HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from puppeteer.