@roman_r_m
Also, have you seen this issue?
That one also is an issue that is affected by whether Joplin is in memory, though it's the other way around: functionality is broken if app is in memory, and works well if it is not. I and @Daeraxa can reproduce. Can you?
I mention it because I wonder if some process is acting differently based on whether Joplin has just loaded or was already in memory, and perhaps that will lead to the root cause of both the problem described here, and the one I linked to above. Perhaps looking at that will be a simpler way to locate the issue.