Infeasible
Status Update
No update yet.
Comments
ra...@google.com
I see same issue and have been debugging it.
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
NOTE: It DOES NOT happen if not using support package, but use android level 14/15 library. I believe Honeycomb works well too.
My current workaround is to provide my own DialogFragment.show() method, like below:
public int show(FragmentTransaction transaction, String tag) {
return show(transaction, tag, false);
}
public int show(FragmentTransaction transaction, String tag, boolean allowStateLoss) {
transaction.add(this, tag);
mRemoved = false;
mBackStackId = allowStateLoss ? transaction.commitAllowingStateLoss() : transaction.commit();
return mBackStackId;
}
ra...@google.com
[Comment deleted]
ra...@google.com
But Google pls fix this issue, as the expected behaviors must be consistent with ICS DialogFragment + FragmentManager and support package DialogFragment + FragmentManager.
It happens with both Support Package v4 r6 and v13 r6.
It happens with both Support Package v4 r6 and v13 r6.
mu...@gmail.com
I have this problem too.
As a workaround I use a boolean in the onActivityResult to mark the desired dialog and show the dialog in the onResume.
As a workaround I use a boolean in the onActivityResult to mark the desired dialog and show the dialog in the onResume.
Description
06-07 02:38:55.205 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:39:05.206 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:39:15.207 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:39:25.208 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:39:35.208 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:39:45.210 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:39:55.211 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:40:05.213 17800 19442 E libunwindstack: Timeout waiting for ucontext
06-07 02:40:15.215 17800 19442 E libunwindstack: Timeout waiting for ucontext
```
I am not sure how the app enters this state, but DefaultDispatcher (kotlin) keeps increasing, as does the CPU use. There are were no logs from the app despite CPU use trending towards 100% except a few from the ConnectivityService observer on NetworkRequestCallbacks.
```
06-07 02:41:25.224 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.228 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.229 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.229 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.230 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.231 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.232 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.233 17800 19602 D ConnectivityEvents: onCapabilitiesChanged, 467262165005, 108
06-07 02:41:25.234 17800 19602 D ConnectivityEvents: onLinkPropertiesChanged: 467262165005, 108
06-07 02:41:25.235 17800 19602 D ConnectivityEvents: onLinkPropertiesChanged: 467262165005, 108
06-07 02:41:25.545 752 752 I tombstoned: received crash request for pid 17800
06-07 02:41:25.549 17800 19442 I elzero.bravedns: Wrote stack traces to tombstoned
06-07 02:41:25.550 752 752 E tombstoned: Traces for pid 17800 written to: trace_02
06-07 02:41:28.240 17800 19603 D ConnectivityEvents: networkSet size: 1
06-07 02:41:28.242 17800 19603 I ConnectivityEvents: Connected network: 467262165005 Cellular, new? false, force? true, test? false
06-07 02:41:28.243 17800 19603 D ConnectivityEvents: processing active network: 108
```
The app started printing traces from other components after I sent sigterm (15), but it wasn't responsive as before (pitch black screen on opening the launcher activity).
```
06-07 02:41:28.251 17800 19603 D VpnLifecycle: old: 1500, new: 1500, oldaux: 1280 newaux: 1280
06-07 02:41:28.251 17800 19603 D VpnLifecycle: r6: underlyingNetworks: true, 1
06-07 02:41:28.251 17800 19603 I VpnLifecycle: r6: Active network ok: ov: false
06-07 02:41:28.251 17800 19603 D VpnLifecycle: r4: useActive? true, sz: 1
06-07 02:41:28.252 17800 19603 I VpnLifecycle: r4: reachable, ov: true
06-07 02:41:28.252 17800 19603 I VpnLifecycle: Building vpn for v4? true, v6? false
```
This happened on Android 14 (Security update: 5 Apr 2024; Kernel: 4.19.191+, OnePlus Build ID: U90P00BRB1EX01) running on CPH2401 (OnePlus Nord 2T).
I haven't been able to reproduce it since.