WAI
Status Update
No update yet.
Comments
an...@gmail.com
I'm pretty far from being a C++ expert, but I think this may be due to holding a reference to the Config beyond it's lifetime?
See StartDiscovery():
void StartDiscovery() {
...
g_state->task_runner->PostTask([]() {
// optional<Config> created here
auto config = GetConfigForAllInterfaces();
if (!config) {
return;
}
// long-lived reference of config given to OpenScreen
g_state->service = discovery::CreateDnsSdService(g_state->task_runner.get(),
g_state->reporting_client.get(), *config);
for (int i = 0; i < kNumADBDNSServices; ++i) {
auto receiver = std::make_unique<ServiceReceiver>(
g_state->service.get(), kADBDNSServices[i], OnServiceReceiverResult);
receiver->StartDiscovery();
...
}
...
// config destructed here
});
}
ad...@google.com
ad...@google.com
A word on impact:
- We rely on WiFi debugging because we use the USB port for additional devices.
- This has made WiFi based debugging unreliable and painful to use because when ADB crashes the connection is lost and is not automatically re-created. Often it can required manually toggling WiFi debugging on the tablet.
ad...@google.com
I've left Wireshark running over the weekend to detect truncated MDNS queries and can confirm they are killing ADB. The truncated messages seem like valid network traffic, so it shouldn't be killing ADB.
Attached are wireshark records in a screenshot which line up with the ADB logs (timezone is Adelaide +10:30):
daniel@RES-0128:/ressys/maxedge$ cat /tmp/adb.5005.log | grep -ie Bridge -e OSP | tail
01-15 00:02:38.265 37828 37828 F adb : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0:
01-15 00:02:41.413 37846 37846 I adb : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 07:58:02.786 37846 37846 F adb : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0:
01-15 07:58:05.928 40026 40026 I adb : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 08:02:46.408 40026 40026 F adb : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0:
01-15 08:02:48.548 40054 40054 I adb : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 08:11:55.906 40054 40054 F adb : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0:
01-15 08:11:59.048 40092 40092 I adb : main.cpp:63 Android Debug Bridge version 1.0.41
01-15 08:48:03.117 40092 40092 F adb : logging.cpp:39 OSP_CHECK((max_allowed_messages_) > (0)) failed: 0 vs. 0:
01-15 08:48:06.280 41928 41928 I adb : main.cpp:63 Android Debug Bridge version 1.0.41
Description
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
What type of Android issue is this? Wi-Fi
What steps would let us observe this issue?
1. Connect Pixel 6 Pro to LAN over WiFi (dynamic IP via DHCP)
2. Have router defined to DHCP with a reachable DNS server for IPv4, and an unreachable one for IPv6
3. Disconnect/reconnect Pixel to said WiFi in order to get updated DNS servers from DHCP (with the unreachable/invalid IPv6 one)
What did you expect to happen?
Pixel stays connected to Wifi and is able to reach hosts for which IPv4 DNS resolution was needed (and succeeded). However, resolution of IPv6 DNS lookups will fail and unknown hostname error or similar expected.
What actually happened?
Pixel jumps back and forth between Wifi and 4G. Instantly fixed (stays connected to WiFi) as soon as DNS IPv6 is restored to a valid/reachable server. This issue is not visible on iphone. Also, private DNS automatic or off don't have any influence on this issue, which persists no matter which option is selected.
How often has this happened?
Every time
What was the effect of this issue on your device usage, such as lost time or work?
High
Additional comments
Issue makes it hard to stay connected and browse LAN resources since LAN connection is continuously interrupted.
Debugging information
Google Play Services
com.google.android.gms
Version 220615044 (22.06.15 (190400-428792003))
System App (Updated)
Android System WebView
com.google.android.webview
Version 484405834 (99.0.4844.58)
System App (Updated)
Network operator: F SFR
SIM operator: SFR
Filed by Android Beta Feedback. Version (Updated): 2.24-betterbug.external_20220211_RC01
To learn more about our feedback process, please visit