Device Farm stops working after a while with higher load

[shadow2720]

Describe the bug

I´m running device-farm 9.4.17 with 11 physical Android phones connected. Everything is running under Debian 12.
I´m facing problems with initialization of session when I launch tests on 4 or more phones at once after a while of using (few hours usually) it. Device Farm cannot correctly init new session, there is a timeout installing stream.apk usually but it can hung on other ADB command as well. However the device IS NOT marked as free again. It is constantly marked as Busy even tho there is nothing to go on there.

So basicaly I have two problems:

• device-farm is not able to install stream.apk and I have no idea why because there is no relevant log
• device-farm keeps device marked as Busy even tho there is nothing going on there

I did not have these issues (mainly second one) on versions of device farm that were not using stream.apk

Tested with variety of physical devices, different Android versions.

Link to Appium logs

Since the log file has more then 2GB, I´m putting here just a short snipped with error where I would expect the device to be marked as not-busy when installation fails:
logs.txt

Environment

1. Appium version (or git revision) that exhibits the issue: 2.14.1
2. Last Appium version that did not exhibit the issue (if applicable): -
3. Node.js version (unless using Appium.app|exe): -
4. Npm or Yarn package manager: -
5. Mobile platform/version under test: Android 10+
6. Real device or emulator/simulator: real devices
7. Appium CLI or Appium.app|exe:

[sudharsan-selvaraj]

@shadow2720 The second issue might be a side effect of the ADB timeout error occurring during the stream APK installation. To rule this out, you can disable the stream app installation by setting df:liveVideo to false and check if the error persists. In the meantime, we will investigate further to identify any other potential issues.