Triliumnotes is painfully slow to edit a note

[deajan]

Description

I've updated my windows TriliumNotes client to current v0.100 today.
Later, I began writing a note.
After a couple of minutes, everytime I write, trilium's interface becomes slow, the writing is really laggy, and it looks like my CPU is eaten by trilium.

[QUICK SIDE NOTE]:
I created a new subnote, and then all notes in my current tab looked like the note I was editing first , ie I could naviagate to any note, the main screen wouldn't update (I extracted the backend logs since this looked like a ckeditor problem, please find them attached). I've closed and re-opened trilium, notes look like they should again.
[/END OF SIDE NOTE]

I work on a Xeon E-2286M laptop which otherwise works great, so the slow interface isn't hardware related.
I've closed and re-opened trilium a couple of times, I can easily replicate the slowness.
When I type something (see the superbe text I wrote in the red square from the screenshot), trilium makes my CPU spike.

Willing to share my note (it's only technical stuff) in order to replicate issue.

TriliumNext Version

0.100-0

What operating system are you using?

Windows

What is your setup?

Local + server sync

Operating System Version

Win10 22H2

Error logs

15:37:55.878 204 PUT /api/options with 0 bytes took 1ms
15:38:00.971 200 POST /api/tree/load with 4711 bytes took 0ms
15:38:00.994 200 GET /api/sql/schema with 7987 bytes took 1ms
15:38:01.010 200 GET /api/notes/_backendLog/blob with 157 bytes took 1ms
15:38:01.015 JS Error: Uncaught error: Message: Uncaught CKEditorError: marker-destroyed
Read more: https://ckeditor.com/docs/ckeditor5/latest/support/error-codes.html#error-marker-destroyed, URL: http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js, Line: 1, Column: 66029, Error object: {"context":{"name":"mention","usingOperations":false,"affectsData":false},"name":"CKEditorError"}, Stack: CKEditorError: marker-destroyed
Read more: https://ckeditor.com/docs/ckeditor5/latest/support/error-codes.html#error-marker-destroyed
at po.getRange (http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js:5:165902)
at target (http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js:25:258161)
at Hu (http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js:13:64272)
at nt.attachTo (http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js:13:58506)
at listenTo.useCapture (http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js:13:59744)
at dL.fire (http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js:3:1390)
at HTMLDocument.t (http://127.0.0.1:37840/assets/v0.100.0/src/ckeditor5.js:3:10489)
Stack: Error
at Object.logError$1 [as logError] (http://127.0.0.1:37840/assets/v0.100.0/src/app_context.js:28:80574)
at Ke.window.onerror (http://127.0.0.1:37840/assets/v0.100.0/src/index_jquery.js:1:960)
15:38:01.064 204 PUT /api/options with 0 bytes took 0ms
15:38:01.069 200 GET /api/notes/_backendLog/attachments with 2 bytes took 0ms
15:38:01.070 200 GET /api/note-map/_backendLog/backlink-count with 11 bytes took 0ms

[dosubot]

This lag and high CPU usage is caused by a known bug in CKEditor 5, which Trilium uses for note editing. The error you see—CKEditorError: marker-destroyed—happens when CKEditor's internal marker management (used for features like mentions and syntax highlighting) gets out of sync, often after editing notes with mentions, large code blocks, or lots of formatting. This can cause the editor to become unresponsive or very slow, and sometimes the UI stops updating until you restart the app. This is not related to your hardware or OS, and restarting only temporarily helps because the underlying bug is still present source.

Trilium recently updated to CKEditor 47.2.0, but this specific marker-destroyed issue is not yet fixed upstream source. The problem is most likely triggered by the mention feature (the @ autocomplete), custom plugins, or large/complex notes source.

You can try these workarounds to reduce crashes and lag:

• In Trilium's Options → Text Notes, disable "Enable Emoji auto-completion" and "Enable Slash Commands"—these plugins are known to cause related issues source.
• Avoid using very large code blocks or excessive mentions in a single note if possible.
• Make frequent manual saves or backups, especially when working on important or large notes, since autosave may not always catch changes before a crash source.
• If you use external syntax highlighting widgets, remove them—Trilium has built-in syntax highlighting, and external modules can interfere source.

If you can share the problematic note (or describe its structure, e.g., lots of mentions, code, or special formatting), it may help pinpoint the exact trigger.

Ultimately, a permanent fix depends on the CKEditor team resolving this bug upstream. Once they do, it will be included in a future Trilium update source.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[eliandoran]

@deajan , did you experience this slowdown and crashes only with this particular note?
Either way, please provide the note so that I can try to replicate it on my side as well.

[eliandoran]

@deajan , the slowdown occurred while editing a code block?
I wonder if it's the same as #7057.

[deajan]

Please find the attached note Stack LAMP AIO.zip

Indeed, I got this while trying to edit a rather large code block.
I didn't notice any other lagging for other notes I use to edit.

Willing to make tests if needed.