What happened?
A bug happened!
I'll send another more detailed summary of how many labels I have and notes (both are a lot).
Also, I'll possibly submit a log from LogFox or something like that as well. Please tell me what would be most helpful?!.
I have been dealing with the same exact crash issue on both the brand new S26 Ultra {n Android 17 and this old Galaxy S20 (both AT&T locked models and firmwares).
Is there anything you're able to ascertain from the provided log?
If there's Anything that I can check on my end or provide, please let me know as I'm going to have to use Obsidian as my daily driver even though it's slower because the crashes are so constant. I've noticed the one thing that helps is to type each character in the search slowly, one at a time every 3 seconds or so, I type in the search too quickly it then is almost guaranteed to crash. Though the app also crashes randomly while in the middle of editing or creating a note.
Another frustration is that it's easy to accidentally convert a note into a task list and then when I go to convert it back, it loses all its formatting.
I know the mentioned bugs/issues aren't in the most coherent order but only have time to mention them as they come to mind as there have been multiple issues over the past year of use.
I look forward to hearing back and hope that what I've provided will help in fixing any bugs or in the coding of future releases. Thanks
App Version
7.11.2
Android Version (API Level)
33
(Optional) Relevant log output
java.lang.OutOfMemoryError: Failed to allocate a 152 byte allocation with 181256 free bytes and 177KB until OOM, target footprint 268435456, growth limit 268435456; giving up on allocation because <1% of heap free after GC.
at android.view.accessibility.AccessibilityEvent.obtain(AccessibilityEvent.java:1349)
at android.view.ViewRootImpl$SendWindowContentChangedAccessibilityEvent.run(ViewRootImpl.java:12603)
at android.os.Handler.handleCallback(Handler.java:942)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:226)
at android.os.Looper.loop(Looper.java:313)
at android.app.ActivityThread.main(ActivityThread.java:8762)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:604)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1067)
What happened?
A bug happened!
I'll send another more detailed summary of how many labels I have and notes (both are a lot).
Also, I'll possibly submit a log from LogFox or something like that as well. Please tell me what would be most helpful?!.
I have been dealing with the same exact crash issue on both the brand new S26 Ultra {n Android 17 and this old Galaxy S20 (both AT&T locked models and firmwares).
Is there anything you're able to ascertain from the provided log?
If there's Anything that I can check on my end or provide, please let me know as I'm going to have to use Obsidian as my daily driver even though it's slower because the crashes are so constant. I've noticed the one thing that helps is to type each character in the search slowly, one at a time every 3 seconds or so, I type in the search too quickly it then is almost guaranteed to crash. Though the app also crashes randomly while in the middle of editing or creating a note.
Another frustration is that it's easy to accidentally convert a note into a task list and then when I go to convert it back, it loses all its formatting.
I know the mentioned bugs/issues aren't in the most coherent order but only have time to mention them as they come to mind as there have been multiple issues over the past year of use.
I look forward to hearing back and hope that what I've provided will help in fixing any bugs or in the coding of future releases. Thanks
App Version
7.11.2
Android Version (API Level)
33
(Optional) Relevant log output