Fixed
Status Update
No update yet.
Comments
ma...@google.com
ka...@mercari.com
Thank you for your submission. Can you provide the idea.log file from (help> show log > idea.log). Also provide the addition information like Android Studio version & OS (Android Studio menu > About) along with additional steps to replicate the issue (if any?)
This will help ensure the team can correctly triage and reproduce your issue.
If we do not get an update in the next 30 days we will close this issue.
This will help ensure the team can correctly triage and reproduce your issue.
If we do not get an update in the next 30 days we will close this issue.
an...@google.com
This has so far only happened on CI using AGP 3.2.0 so there are no Android Studio logs.
ka...@mercari.com
Hello, is there any update on this issue?
ap...@google.com
Yigit: FYI compiling seems to be busted with parallel compilation?
Jerome: Anything we should be doing special for parallel compilation?
Jerome: Anything we should be doing special for parallel compilation?
ap...@google.com
thats weird, jetifier fails to read its own resources. :/.
an...@google.com
ka...@mercari.com
I presume that the parallel execution makes it to choke on the same stream (= file descriptor) when loading the config from multiple threads.
I'm looking at the usage in databinding where I can see this:
private val typeRewriter by lazy(LazyThreadSafetyMode.NONE) {
val config = ConfigParser.loadDefaultConfig()
}
I presume that LazyThreadSafetyMode.NONE might be the issue? As that might probably trigger multiple accesses to the same config file at the same time?
I'm looking at the usage in databinding where I can see this:
private val typeRewriter by lazy(LazyThreadSafetyMode.NONE) {
val config = ConfigParser.loadDefaultConfig()
}
I presume that LazyThreadSafetyMode.NONE might be the issue? As that might probably trigger multiple accesses to the same config file at the same time?
st...@google.com
we don't really do multi threading so it is lazy because we don't want to pre-allocate it until needed.
na...@google.com
I don't understand what you mean by not doing multithreading. Gradle build indeed does multhithreading as you can se above on the parallel build.
al...@mercari.com
We just looked into it with Hung and the solution should be to have the config file as a singleton in the LibTypes. Right now the parallel build makes it load several configs in parallel which causes that it chokes on the file stream.
an...@google.com
I just submitted a fix for this (Change-Id: I2675640875bcae7e5f1346de8c12acb3a0379902).
The fix will be available in AGP 3.5.0-alpha05. Please try it out when it's released, and let us know if you still run into this issue.
The fix will be available in AGP 3.5.0-alpha05. Please try it out when it's released, and let us know if you still run into this issue.
Description
Jetpack Compose version: 1.3.0 & 1.4.0-alpha02
Android Studio Build: IntelliJ IDEA 2022.2.3
Kotlin version: 1.7.10
Steps to Reproduce or Code Sample to Reproduce:
We're seeing an issue where a Lazy layout with a BoxWithConstraints in the
itemwill add new items to the saved bundle every time the user scrolls. The entries appear to be AbsSavedState.EMPTY_STATE, but there are so many of them that the bundle fills up quickly and can cause a "TransactionTooLargeException".I've attached a sample project demonstrating the issue. The issue only appears on Android 9, and the sample project does not exhibit the issue in either Android 8.1 or Android 10. Nor does the issue happen when swapping BoxWithConstraints with Box. Also it appears to have been introduced some point after Compose 1.2.0, as the sample also doesn't experience the issue on Android 9 when using Compose 1.2.0.