Assigned
Status Update
Comments
an...@google.com <an...@google.com>
ch...@google.com <ch...@google.com> #2
This only affects 1.4-alphaX and is a side-effect of aosp/2267993
ch...@google.com <ch...@google.com> #3
Assigning this to Leland as it doesn't look related to the above change.
vi...@google.com <vi...@google.com> #4
We are still affected by this bug. Is it really P4?
vi...@google.com <vi...@google.com> #5
Would any other formulation of the same behavior work around the bug in the short term?
vi...@google.com <vi...@google.com> #6
In my testing using recursion instead of a while loop avoids the issue, with some theoretical risk of stack overflow.
as...@google.com <as...@google.com> #7
Which version of Compose are you using? We fixed a lot of issues with this imbalance in Compose runtimve 1.4.1 and 1.5.
Description
REMEMBER: a bug should be understandable years later by someone who will never talk to the reporter or assignee.]
STEPS TO REPRODUCE:
1. Invoke the following function during composition:
@Composable
operator fun invoke(uiElement: Any): Any {
var value = uiElement
while (true) {
val converter: (@Composable (Any) -> Any)? = null
if (converter == null) {
return value
} else {
val converted = converter(value)
if (converted == value) {
return value
} else {
value = converted
}
}
}
}
EXPECTED RESULTS:
No crash
OBSERVED RESULTS:
androidx.compose.runtime.ComposeRuntimeError: Compose Runtime internal error. Unexpected or incorrect use of the Compose internal runtime API (Start/end imbalance). Please report to Google or use
ADDITIONAL INFORMATION:
Device: Pixel 2 API 31 emulator
Build #: sdk_goog3_x86_64-userdebug 12 SQ1A.220205.001.Z2 9132735 dev-keys