https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
v

vgonda

07/05/2022, 3:48 PM
So, it is a feature or a bug that in
ComposeTest
the lifecycle aware composer is replaced with one controlled by the test? As far as I can tell, this makes it such that things aren't disposed when they would be outside a test environment, and it's causing us memory leaks in the test. More details in the thread.
We have this test rule chain set up. However, there currently isn't a way to introduce the compose test rule without either: 1. Erroring because an activity was launched before the compose test rule started 2. Erroring because we detect leaks before the compose rule disposes things.
Leak trace incoming
┬───
│ GC Root: Thread object
│
├─ android.app.Instrumentation$InstrumentationThread instance
│    Leaking: NO (PathClassLoader↓ is not leaking)
│    Thread name: 'Instr: com.company.InstrumentationRunner'
│    ↓ Thread.contextClassLoader
├─ dalvik.system.PathClassLoader instance
│    Leaking: NO (WindowRecomposerPolicy↓ is not leaking and A ClassLoader is never leaking)
│    ↓ ClassLoader.runtimeInternalObjects
├─ java.lang.Object[] array
│    Leaking: NO (WindowRecomposerPolicy↓ is not leaking)
│    ↓ Object[2289]
├─ androidx.compose.ui.platform.WindowRecomposerPolicy class
│    Leaking: NO (a class is never leaking)
│    ↓ static WindowRecomposerPolicy.factory
│                                    ~~~~~~~
├─ java.util.concurrent.atomic.AtomicReference instance
│    Leaking: UNKNOWN
│    Retaining 12 B in 1 objects
│    value = instance of androidx.compose.ui.test.AndroidComposeTest$withWindowRecomposer$1 anonymous class implementing androidx.compose.ui.platform.WindowRecomposerFactory
│    ↓ AtomicReference.value
│                      ~~~~~
├─ androidx.compose.ui.test.AndroidComposeTest$withWindowRecomposer$1 instance
│    Leaking: UNKNOWN
│    Retaining 12 B in 1 objects
│    Anonymous class implementing androidx.compose.ui.platform.WindowRecomposerFactory
│    ↓ AndroidComposeTest$withWindowRecomposer$1.this$0
│                                                ~~~~~~
├─ androidx.compose.ui.test.AndroidComposeTest instance
│    Leaking: UNKNOWN
│    Retaining 434 B in 15 objects
│    ↓ AndroidComposeTest.testCoroutineDispatcher
│                         ~~~~~~~~~~~~~~~~~~~~~~~
├─ kotlinx.coroutines.test.UnconfinedTestDispatcherImpl instance
│    Leaking: UNKNOWN
│    Retaining 20 B in 1 objects
│    ↓ UnconfinedTestDispatcherImpl.scheduler
│                                   ~~~~~~~~~
├─ kotlinx.coroutines.test.TestCoroutineScheduler instance
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79814 objects
│    ↓ TestCoroutineScheduler.events
│                             ~~~~~~
├─ kotlinx.coroutines.internal.ThreadSafeHeap instance
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79807 objects
│    ↓ ThreadSafeHeap.a
│                     ~
├─ kotlinx.coroutines.internal.ThreadSafeHeapNode[] array
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79806 objects
│    ↓ ThreadSafeHeapNode[0]
│                        ~~~
├─ kotlinx.coroutines.test.TestDispatchEvent instance
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79805 objects
│    ↓ TestDispatchEvent.marker
│                        ~~~~~~
├─ kotlinx.coroutines.test.CancellableContinuationRunnable instance
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79803 objects
│    ↓ CancellableContinuationRunnable.continuation
│                                      ~~~~~~~~~~~~
├─ kotlinx.coroutines.CancellableContinuationImpl instance
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79802 objects
│    ↓ CancellableContinuationImpl.delegate
│                                  ~~~~~~~~
├─ kotlinx.coroutines.internal.DispatchedContinuation instance
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79793 objects
│    ↓ DispatchedContinuation.continuation
│                             ~~~~~~~~~~~~
├─ androidx.compose.foundation.ClickableKt$handlePressInteraction$2$delayJob$1 instance
│    Leaking: UNKNOWN
│    Retaining 3.2 MB in 79792 objects
│    Anonymous subclass of kotlin.coroutines.jvm.internal.SuspendLambda
│    ↓ ClickableKt$handlePressInteraction$2$delayJob$1.$delayPressInteraction
│                                                      ~~~~~~~~~~~~~~~~~~~~~~
├─ androidx.compose.runtime.ParcelableSnapshotMutableState instance
│    Leaking: UNKNOWN
│    Retaining 3.1 MB in 79782 objects
│    ↓ SnapshotMutableStateImpl.next
│                               ~~~~
├─ androidx.compose.runtime.SnapshotMutableStateImpl$StateStateRecord instance
│    Leaking: UNKNOWN
│    Retaining 3.1 MB in 79781 objects
│    ↓ SnapshotMutableStateImpl$StateStateRecord.value
│                                                ~~~~~
├─ androidx.compose.foundation.ClickableKt$clickable$4$delayPressInteraction$1 instance
│    Leaking: UNKNOWN
│    Retaining 36 B in 2 objects
│    Anonymous subclass of kotlin.jvm.internal.Lambda
│    ↓ ClickableKt$clickable$4$delayPressInteraction$1.$isRootInScrollableContainer
│                                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
├─ androidx.compose.foundation.Clickable_androidKt$isComposeRootInScrollableContainer$1 instance
│    Leaking: UNKNOWN
│    Retaining 16 B in 1 objects
│    Anonymous subclass of kotlin.jvm.internal.Lambda
│    ↓ Clickable_androidKt$isComposeRootInScrollableContainer$1.$view
│                                                               ~~~~~
├─ androidx.compose.ui.platform.AndroidComposeView instance
│    Leaking: YES (View.mContext references a destroyed activity)
│    Retaining 3.1 MB in 79772 objects
│    View not part of a window view hierarchy
│    View.mAttachInfo is null (view detached)
│    View.mWindowAttachCount = 1
│    mContext instance of flow.path.FlowPathContextWrapper, wrapping activity com.company.MainActivity with mDestroyed = true
│    ↓ AndroidComposeView._autofill
├─ androidx.compose.ui.autofill.AndroidAutofill instance
│    Leaking: YES (AndroidComposeView↑ is leaking)
│    Retaining 20 B in 1 objects
│    ↓ AndroidAutofill.autofillManager
├─ android.view.autofill.AutofillManager instance
│    Leaking: YES (AndroidComposeView↑ is leaking)
│    Retaining 103 B in 4 objects
│    mContext instance of com.company.MainActivity with mDestroyed = true
│    ↓ AutofillManager.mContext
╰→ com.company.MainActivity instance
     Leaking: YES (ObjectWatcher was watching this because com.company.MainActivity received Activity#onDestroy() callback and Activity#mDestroyed is true)
     Retaining 27.2 kB in 1079 objects
     key = c4271098-7bee-44b7-8c39-72e70a1dceec
     watchDurationMillis = 6358
     retainedDurationMillis = 1358
     mApplication instance of com.company.MyTestApp
     mBase instance of androidx.appcompat.view.ContextThemeWrapper
cc/ @Zach Klippenstein (he/him) [MOD] @py
z

Zach Klippenstein (he/him) [MOD]

07/05/2022, 4:32 PM
@Jelle Fresen [G]
p

py

07/06/2022, 6:17 AM
Btw these leaks manifest because an AndroidComposeView is removed from the view hierarchy (as part of normal navigation in the test) before end of test & activity destroy.
The compose test rule cleans up its bad references at the end of the test.. better than no cleaning up, but still not good. All refs to a view should be let go as soon as its detached.
Mmm re reading the trace maybe I got that one wrong as it seems the activity is destroyed here. Same principle though, activities come and go during a test, cleanup should happen as soon as activities are gone and not just at the end of a test rule
z

Zach Klippenstein (he/him) [MOD]

07/06/2022, 4:48 PM
Please file a bug - or did you file one for the symptom? I can update it with these details if you don’t have permission
v

vgonda

07/06/2022, 8:13 PM
I have not filed a bug yet. I can file one!
@Ian G. Clifton