Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add temporary crash handler for Flictionary OOM errors until 0.3.15

See original GitHub issue

Short description

Describe what you were doing that could’ve led to the crash.

Steps to reproduce

I can’t reproduce the error, just I opened firefox, the florisboard is still working, it dosen’t return to the default keyboard

Environment information

FlorisBoard Version: 0.3.13-beta10 (53)
Device: Samsung SM-A505F A50
Android: 11 (cn=R sdk=30)

Features enabled

smartbar = true
suggestions = true
suggestions_clipboard = true
suggestions_next_word = true
glide = false
clipboard_internal = true
clipboard_history = false

Attached stacktrace files

1629670378948.stacktrace

java.lang.OutOfMemoryError: Failed to allocate a 32 byte allocation with 42800 free bytes and 41KB until OOM, target footprint 268435456, growth limit 268435456; failed due to fragmentation (largest possible contiguous allocation 95420416 bytes)
	at dev.patrickgold.florisboard.ime.dictionary.Flictionary$Companion.load-B7oiUAE(Flictionary.kt:135)
	at dev.patrickgold.florisboard.ime.dictionary.DictionaryManager.loadDictionary-pqiQ7go(DictionaryManager.kt:94)
	at dev.patrickgold.florisboard.ime.text.TextInputManager$onWordHistoryChanged$1.invokeSuspend(TextInputManager.kt:1001)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:571)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:678)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)
:678)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:665)

Issue Analytics

State:
Created 2 years ago
Comments:10 (4 by maintainers)

Top GitHub Comments

1reaction

patrickgoldcommented, Aug 22, 2021

I’ve renamed this issue as I will address this before stable 0.3.13.

0reactions

patrickgoldcommented, Aug 25, 2021

The crash logs you sent me all have the same culprit: you have word suggestions enabled. Sadly for your device it simply does not work for now, so to at least use all other features of FlorisBoard it would be best if you disable word suggestions until 0.3.15.