Joplin: Android: Memory leak?

[TobiasDev]

Operating system

• Android

Application

• Mobile

Bug

Whenever I write for a longer time in Joplin on my OnePlus 3 it starts to lag a lot after a while.

I've tried several other writing apps to make sure it isn't my keyboard or such that has the memory leak, but I only see the issues happening when writing in Joplin.

This usually doesn't take to long after I begin to write, usually within the first 5 minutes.

If I can help with any kind of debugging let me know here and I'll do what I can.

[hagbartus]

I am facing the same issue, OnePlus 3T here. It's really annoying and not fun the use the app after some (quite short) time.
If you want me to do some logging / tests, please let me know.

[laurent22]

Is that the issue you're having? https://github.com/facebook/react-native/issues/20119

[TobiasDev]

Yeah, that is the one!

[m-p-3]

I suffer from this issue on my Mi A1 (Android 9), and so far the only workaround I've found is a reboot. Anything else I can do to avoid rebooting?

[TobiasDev]

@m-p-3 I believe the only thing you can do is poke in the linked issue from Laurent22. It is a bug in the library and not in Joplin

[foxmask]

I'm in a situation where, now, I fear to edit / add note on android, because this problem happens each time I enter a complet sentance. (eg a todo list)
As soon as I meet this issue, I have to restart the mobile, because the keyboard (handled by gboard app) is become unusable too. :/

[laurent22]

The RN issue that tracks this problem is apparently high priority but looks like it hasn't been fixed yet. I'll upgrade relatively soon RN anyway and we'll see if it's any better.

[virtadpt]

Would downgrading to v0.49 be an option? Reading those bug tickets, that seems to be the last rev that didn't have the slowdown bug.

[foxmask]

I would test it in case, as now I can just do one thing , reading content, not adding otherwise I have to reboot the smartphone

[laurent22]

Perhaps some hope? https://github.com/facebook/react-native/issues/20119#issuecomment-576917362

[foxmask]

Because of that, I do not use Joplin for months. I had to move on markor/syncthing :(

[laurent22]

Because of that, I do not use Joplin for months. I had to move on markor/syncthing :(

yes it seems to affect some people more than other, maybe depending on the device or note.

[laurent22]

Apparently the text input component was completely rewritten using React hooks so that might be good news for us. Hopefully someone can confirm this.

[laurent22]

Seems it's been confirmed - https://github.com/facebook/react-native/issues/20119#issuecomment-578650379 Now it's "only" a matter of upgrading to the latest version of React Native.

[foxmask]

that's smell good

[haeringer]

Happy to see there's a fix in sight, because I'm hardly able to use the app on my Mi A2/Android 10 device right now. Would close issue #1209 too.

[AlexandreBrown]

Same issue also occurs on desktop.
When typing relatively small notes in 1 go, (~1700 characters with maths markdown expressions), the app becomes very slow and there is a big delay when typing (I have to wait a 200ms-1000ms before each char)

I suspect this is related to this memory leak issue because when I kill the app and restart it it fixes the issue.

OS: Ubuntu 20.04
CPU: i7 6700k
RAM: 32GB
Storage: NVMe SSD

[virtadpt]

It's still a problem for the Android version (Joplin v1.0.324v database v28) running on a Samsung SM-G965U (Android v10). Is there any hope in sight?

[erichiller]

Same here - Samsung S8

[jbcurtin]

I've experienced a slowdown in the application on my phone too when ever the note reaches 3+ paragraphs. Any status on improving the performance of the typing on Android?

( btw, @laurent22 , we can't see if anything is being discussed in the thread @roman-r-m mentioned )

[GreatestFool]

This should seriously be looked into faster, what is the point of being able to edit if the application is to slow for it?

On my S5e I'm experiencing enough lag that it starts skipping inputs if I don't write at a literal snails pace. It takes about one to two second for each input to even be added, which when combined with then input skipping does not make for a pretty view.

As of now, the mobile application is atrocious for anything more than previewing notes.

[virtadpt]

Ticket closed, 21 April... this is why I stopped using Joplin. It's completely unusuable. I thought I unsubbed from this ticket thread.

[Zie0]

OnePlus 3T user here. This has impacted me for months, ever since I started depending on Joplin for note taking. When I have a longer note there is no use in using the android app and I must switch to desktop. Decided to reproduce it today

Summary

I reproduced this today on the Joplin android app after typing random text into the "Add body" section of a new note non-stop for 2 min 37sec on a OnePlus 3T

Confirmed this appears closely related to React Issue 20119

Steps to reproduce:

1. start timer
2. open joplin for android on OnePlus 3T
3. create new note
4. select "Add body" section of the note
5. continue to inputting random chars non-stop until the framerate dropped and a noticeable lag (seconds) between typing a char on the virtual keyboard and the char appearing in the note occurred

It took 2:37s for the textInput became slow after typing

Notes

This issue does not seem to be related to the default OnePlus 3T keyboard app either. The keyboard app used to reproduce this is called "MessagEase Keyboard"

I did not write and clear as React Issue 19126 suggests. All text was entered continuously without performing a Select All > Delete and the issue still appeared.

This implies to me that this is more closely related to React Issue 20119

[seth100]

Any update on this?
I'm not able to edit my notes in a normal way, too slow, totally annoying

[chromer030]

On android app is too slow and using 300 mb of ram !!!

[cosminribo]

Maybe this issue should be renamed, to something like:
ReactNative text editing extremely slow for text input.
The 0.63 version, used in the latest Joplin app did not solve the problem. For the moment, I'm using a different editor, and copy text to Joplin.

[laurent22]

I've just noticed an interesting technique mentioned in the upstream bug: https://github.com/facebook/react-native/issues/20119#issuecomment-714545951 Could be worth a try.