What happened?

I've noticed NotallyX memory allocation growing without bounds under certain circumstances; in one case it actually died with an ENOMEM screen, on a phone where gigabytes of memory should have been available. what I suspect is going on is there's a bug in the string handling code; when this issue has cropped up for me, it's been after spending a few minutes editing a very long note (specifically, 47K long). I've checked under htop and confirmed the leak is reproducible.

if relevant, I'm running this on a rooted Fairphone 3+ under LineageOS 22

App Version

v7.4.2

Android Version (API Level)

15

(Optional) Relevant log output