You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
upgrading your flutter version to 3.7.7 and flutter_webrtc to 0.9.24 might solve this issue.
It’s better this time, but after a while, the following log will appear again and the main screen will be stuck. Then I close the video and open it again to recover. This happens repeatedly.
Now when printing the following log, sometimes it is not stuck and sometimes it will be stuck.
When the screen is stuck, the following log will be printed.
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.7.7, on macOS 13.2.1 22D68 darwin-arm64, locale zh-Hans-CN) Checking Android licenses is taking an unexpectedly long time...[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.76.0)
[✓] Proxy Configuration
[✓] Connected device (4 available)
[✓] HTTP Host Availability
Repeated console output:
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
org.webrtc.Logging(19744): HardwareVideoEncoder: Dropped frame, encoder queue full
flutter:3.7.3
flutter_webrtc: 0.9.23
huawei 4G phone . Harmonys os
Is it the same issue as this one? open-webrtc-toolkit/owt-deps-webrtc#117
The text was updated successfully, but these errors were encountered: