For Android targets, if we enable `LoggingStoreFac...
# mvikotlin
m
For Android targets, if we enable
LoggingStoreFactory
, the Android app eventually crashes due to a JNI global reference table overflow. This crash goes away if we don't use the logging store 🤔. I'm trying to figure out if it's an issue with the library or system print.
a
This is the first time I hear this report. The logger has nothing to do with JNI. It just writes to LogCat, unless you provided a custom logger. 🧐
m
It is perplexing me
a
Let me know if there is a reproducer or something.
m
we are using default logger and default logformatter
We are using
jvm
which appears to be using
println()
a
Yep, nothing fancy is there
Maybe try providing your own logger
🤔 1
m
yeah, it looks like something else is causing the JNI table overflows, just an annoying coincidence that it was hard to repro without logging enabled.
a
Thanks for the update!