Hanged in "Checking is logged..." while launching [ARM64 | Chromium]
See original GitHub issueDescription
Everything works fine until the point “Checking is logged…” and does not proceed beyond that. (No further errors displayed)
NOTE:
- The CPU architecture is ARM64
- This issue is not available in venom-bot@3.1.12
- I have manually installed Chromium using
sudo apt install chromium-browser
whileyarn install
- There is an error stating “executablePath” is undefined. I have been able to fix that by hardcoding the chromium path in
node_modules/venom-bot/dist/controllers/browser.js | Line: 233 and 276
Environment
- Venom version(s): [4.0.0 - 4.0.11]
- Browser: Chromium 101.0.4951.64 snap
- OS: Ubuntu 20.04.4 LTS (ARM64)
- Node version: v16.15.0
Steps to Reproduce
- Install venom-bot
- Start the bot
Log Output
info: [Techie] Waiting... checking the browser...
info: [Techie:browser] Check chromium....
info: [Techie:browser-total] Checking the total bytes to download!
info: [Techie:browser] Chromium Finished result
info: [Techie:browser-total] Chromium completed result
info: [Techie] Error chromium: TypeError: Cannot read properties of undefined (reading 'executablePath')
info: [Techie] Browser successfully opened
info: [Techie] checking headless...
info: [Techie] headless option is active, browser hidden
info: [Techie] Checking page...
info: [Techie] Page successfully accessed
[instance: Techie]: Checking is logged...
Your Code
await venom.create({session:'Techie', useChrome: false}).then((client) => {
_client = client;
})
.catch((error) => {
console.log(error);
});
Additional context / Screenshot
Add any other context about the problem here. If applicable, add screenshots to help explain.
Issue Analytics
- State:
- Created a year ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
[BUG] Chromium crashes on m1 · Issue #13868 - GitHub
[BUG] M1 chip While running Visual regression tests on webkit, the page crashes and it wont take any screenshots #13871.
Read more >354405 - Chrome/Android on Arm64 tracking bug - Monorail
Currently there is no ARM64 support for seccomp_bpf and the content_shell build will fail without this check. BUG=354405, 355125. R=jln@chromium ...
Read more >Google chrome freezes system which is running on RHEL 8.2
I was working on jenkins update through google chrome on this system when it was hanged in last 2 attempts. I am pretty...
Read more >Chromium - ArchWiki
Launch a new browser instance. When you launch the browser, it first checks if another instance using the same data directory is already...
Read more >Release Chromium Android App Bundle to Play Store
Since android has mentioned to release 64bit build after August ... Just checked, this file exists in APK lib\arm64-v8a\crazy.libchrome.so.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@orkestral New observation: When I turned off multidevice (multidevice: false) it works fine. The issue must be connected to the Multi-Device option.
Fix in version 4.1.0