Florisboard has crashed due to an unexpected error
See original GitHub issueShort description
It is completely random I have no idea what caused the problem. I think it is due to clipboard but I am not sure.
Environment information
- FlorisBoard Version: 0.3.13 (56)
- Device: Realme RMX1827
- Android: 10 (cn=Q sdk=29)
Features enabled
smartbar = true
suggestions = true
suggestions_clipboard = true
suggestions_next_word = true
glide = true
clipboard_internal = true
clipboard_history = true
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Florisboard crashed on device startup · Issue #2080
Got an app crash notification when started the device. Steps to reproduce. Shutdown the phone and start it. Once phone is started, observe...
Read more >AnySoftKeyboard | Official website of AnySoftKeyboard, the ...
Official website of AnySoftKeyboard, the open source Android keyboard.
Read more >FlorisBoard - Free and Open Source Android App Repository
FlorisBoard is an open-source keyboard aimed at providing you with an easy way to type while respecting your privacy. Note: This project is...
Read more >Anything other than GBoard out there..? : r/degoogle
FlorisBoard is one. Anysoft keyboard is another. Both FOSS. On the non-FOSS side, SwiftKey is an option. You could use it after turning...
Read more >Android Ultimate Collection & Guides | XDA Forums
Since the thread is too long and gives me error, I split it up on three. ... The system constantly creates logs, crash...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The “unexpected error” everyone n this thread experiences is always the same:
OutOfMemoryError
. As the memory can be full literally with every allocation throughout the codebase, the error will be thrown with completely different looking stacktraces, but all have the same culprit: The Flictionary is loaded in the background and word suggestions allocates too much memory in a short time, to the Garbage collector is not able to cope with it, leading to this crash. Some stacktraces look differently at the beginning, but a few lines down this phrase is included:Caused by: java.lang.OutOfMemoryError:
.I cannot say this enough, but if you experience this issue, make sure to disable word suggestions, restart FlorisBoard and wait for 0.3.15, when a new word suggestions will be implemented.