Error: spawn UNKNOWN" when launching Chrome instances in Playwright

[Nesonica]

Error: spawn UNKNOWN" when launching Chrome instances in Playwright

[jlplenio]

Hmmmm difficult. I think this is a problem with playwright. Could you try with chromium, i.e. comment out this line:
https://github.com/jlplenio/crude-twitch-viewer-bot/blob/8380c49fdeba680c202b124c789c72c7d0abaa03/ctvbot/instance.py#L135C1-L135C30

And try a different browser by changing

crude-twitch-viewer-bot/ctvbot/instance.py

Line 132 in 8380c49

self.browser = self.playwright.chromium.launch(

with e.g. playwright.firefox.launch()

In general, I would recommend you try playwright isolated in a small custom python script. And return to the bot once it works.

And does the executable work from https://github.com/jlplenio/crude-twitch-viewer-bot/releases/latest?

[Nesonica]

Hi @jlplenio ,

I wanted to provide an update on this issue. I've managed to resolve it by switching from using Google Chrome to Mozilla Firefox in the Playwright configuration. Here's how I modified the relevant part of the script:

self.playwright = sync_playwright().start()

self.browser = self.playwright.firefox.launch(
    proxy=proxy_dict,
    headless=self.headless,
    channel="firefox",
    args=[
        "--window-position={},{}".format(self.location_info["x"], self.location_info["y"]),
        "--mute-audio",
    ],
)

This change seems to have resolved the spawn UNKNOWN error I was facing with Chrome. The script now successfully launches a Firefox instance via Playwright.

I'd like to thank the developers for creating and maintaining this project. Your work is greatly appreciated.

I'm now closing this issue as it has been resolved.

Best Regards,
Nes

[jlplenio]

Interesting. Can you confirm that everything is works as expected. Restarts, fresh, kill, screenshot, green status boxes etc.
I was afraid to switch to another browser because I kept seeing in my tests that Twitch behaves differently depending on the browser (layout, cookies, local storage).

And thank you for coming back and presenting your solution. Kudos @Nesonica