Windows10 64 pro here as well with the same issue as described in the video.Especially the Webclipper chrome/firefox extension takes some time to respond too.In the chrome console I see this error
Unchecked runtime.lastError: The message port closed before a response was received.
I don't know if it's related to the lagging though,but in pre 1.1.* versions it had not such issues.
I disabled all extensions , tried again but the same is happening.
Firefox does not complain with an error message but the sluggish behaviour remains there as well.
Hi all, I have downgraded my Joplin to version 1.0.234 and the profile to v.33 (by exporting all my notes to a JEX file and importing it into Joplin 1.0.234). No serious lagging now. So I gather the problem lies with profile version 34.
@terence, in this thread one user solved their performance issue by disabling the spellfix extension. Could you give it a try too to see if it improves perfomances for you too?
I have exactly the same problem. My note collection is manageable i.e. I don't have thousands or tens of thousands of them.
But I do have one note that is very long. In LibreOffice it would be 129 pages at font size 12 pt. It is a list of music tracks and songs, a database would certainly be better for that (would be something for a feature request, Notion supposedly can do that).
When I try to add a new entry, there are always severe delays, whether I'm copying something in or typing.
Spell check is off, but that made no difference. Likewise, it doesn't matter if I just use markup mode or not.
However, when I enable Safe Mode, there is no such delay.
I'm also using Windows 10 Pro, but it's the same with the Mac version (I think, I'll check again).
In Joplin, click on "Help" and there on "Toggle safe mode":
Unfortunately, that's not really a solution or a workaround. If you activate the safe mode all plugins are disabled (e.g. the view mode with formatted text + images). If you need Joplin only for plain text, this is a possibility. Unfortunately it doesn't help that much with troubleshooting, since all plugins are off at once. Some plugin would have to be to blame for the slowdown in editing huge texts as described above.
I thought that with disabled plugins in save mode also modules/functions are meant, because under plugins I have nothing installed. It seems that other things are also disabled in save mode: the WYSIWYG/formatted view mode is disabled, for example. However, the view mode doesn't seem to be the reason for the "editing in slow motion", at least it doesn't make any difference if it's on or off.
Tested! If you turn off all markdown features, then the intervals between the lags become larger when typing. At first you even have the impression that it would be OK now. However, it is only as it should be if you activate the safe mode - as far as I can tell so far. I will leave the safe mode turned on and see if typing really always works without delays.
I can edit the note in Joplin, there are only delays. In an external editor e.g. Windows Editor the problem does not occur. But I do not want to use an external editor.
I have now also tested the latest version* on Mac (High Sierra), where the same problem occurs when editing a large note. The Joplin app on Android also has these severe delays when editing really large notes.
As I said, on Windows and Mac you have normal fast editing with safe mode enabled.
My question now is, what features are disabled in safe mode that have such an effect?
Since creating and editing notes is without a doubt the main function of Joplin, it would be great to get this fixed.
I have experienced a similar situation. After some debugging with dev tools' performance, I have found out the problem is highlightAuto() function. If there is some code part without specified language, Joplin will call highlightAuto() to determine which language it is, and this will take a few seconds if there are five or more code part without language. Safe mode will disable the code render I suppose, so there are no lagging when in safe mode. Didn't know if we have the same problem, if this is the case , don't leave code without language. hope it helps.
