Fixed
Status Update
Comments
kl...@google.com <kl...@google.com>
kl...@google.com <kl...@google.com>
ap...@google.com <ap...@google.com> #2
May I ask why P3? This is blocking for me to go to prod, I'd really like some inputs about what is going on so I can either fix or build a repro to have this fixed.
na...@google.com <na...@google.com> #3
Unfortunately I am unable to reproduce it as well. Maybe there is a chance you can share your code with me? You can send it to my email as you did previously already.
For the ideas on what to take a look, how do you use LazyListState.layoutInfo in your app? Will it continue growing if you comment out such usages?
For the ideas on what to take a look, how do you use LazyListState.layoutInfo in your app? Will it continue growing if you comment out such usages?
Description
LocalSoftwareKeyboardController
,LocalTextInputService
ProvideCommonCompositionLocals
providesLocalSoftwareKeyboardController
andLocalTextInputService
, which are static composition locals. New classes are instantiated every time, which leads to recomposing the entire tree. (ProvideCommonCompositionLocals
gets called when changing language, for example.)Is this desired behavior for some reason, or could we either
LocalSoftwareKeyboardController
andLocalTextInputService
usecompositionLocalOf
instead?textInputService
andsoftwareKeyboardController
to always use the same value if new class instances are not needed?The instantiation of new classes are somewhat hidden in property getter functions here: