webdriverio/webdriverio

[🐛 Bug]: Lot of web-components produce a timeout with Bidi enable

Open

#13,909 建立於 2024年11月22日

在 GitHub 查看
 (5 留言) (0 反應) (0 負責人)JavaScript (6,029 star) (1,793 fork)batch import
Bug 🐛help wanted

描述

Have you read the Contributing Guidelines on issues?

WebdriverIO Version

9.x

Node.js Version

22.x

Mode

Standalone Mode

Which capabilities are you using?

{
      browserName: 'firefox',
      acceptInsecureCerts: true
    }

What happened?

When big components with a lot of dependencies are tested wdio timeout after few seconds:

image

When we disable bidi with wdio:enforceWebDriverClassic': true the test pass directly!

What is your expected behavior?

The browser does not hangout

How to reproduce the bug.

Clone this repo https://github.com/RoXuS/bidi-issue

Install dependencies then launch wdio:

yarn
npx wdio

Firefox is opened then is hangout. If we uncomment enforceWebDriverClassic (https://github.com/RoXuS/bidi-issue/blob/main/wdio.conf.js#L10) then the test passes instantly even if we have a lot of components

Relevant log output

2024-11-22T16:10:04.605Z INFO @wdio/browser-runner: Initiate browser environment
2024-11-22T16:10:04.607Z INFO @wdio/cli:launcher: Run onPrepare hook
2024-11-22T16:10:04.607Z INFO @wdio/utils: Setting up browser driver for: firefox@stable
2024-11-22T16:10:04.607Z INFO @wdio/utils: Setting up browser binaries for: firefox@stable
2024-11-22T16:10:04.706Z INFO @wdio/cli:launcher: Run onWorkerStart hook
2024-11-22T16:10:04.744Z INFO @wdio/browser-runner:ViteServer: Vite server started successfully on port 54728, root directory: /Users/julienrousseau/Documents/works/tmp/bidi-issue
2024-11-22T16:10:04.745Z INFO @wdio/local-runner: Start worker 0-0 with arg: 
2024-11-22T16:10:04.746Z DEBUG @wdio/local-runner: Send command run to worker with cid "0-0"
2024-11-22T16:10:07.524Z DEBUG @wdio/local-runner: Send command workerRequest to worker with cid "0-0"
2024-11-22T16:10:07.557Z DEBUG @wdio/local-runner: Send command workerRequest to worker with cid "0-0"
2024-11-22T16:10:07.563Z DEBUG @wdio/local-runner: Send command workerRequest to worker with cid "0-0"
2024-11-22T16:10:07.568Z DEBUG @wdio/local-runner: Send command workerRequest to worker with cid "0-0"
2024-11-22T16:10:07.615Z DEBUG @wdio/local-runner: Send command workerRequest to worker with cid "0-0"
....

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

貢獻者指南

技術棧
typescriptnodejs
領域
testing
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
active
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
understanding of BiDi protocolfamiliarity with WebdriverIONode.js debugging
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
20
研究方向
Investigate the BiDi implementation in WebdriverIO's Firefox driver. Focus on the `@wdio/browser runner` and `@wdio/protocols` packages. The reproduction repo at https://github.com/RoXuS/bidi issue demonstrates the timeout when many web components are loaded with BiDi enabled. Review the interaction between BiDi message handling and the Vite server. Potentially, the issue may be related to how large responses are processed or a memory leak. Look at the commit history for changes related to BiDi and the Firefox driver.