Typing delay on nixos

[TBS1996]

What happened?

Im brand new to logseq, I made a new directory and Im seeing a very big input delay. It switches between no delay and a big ~(0.2-1) sec delay. I installed it by simply putting logseq into my configurations.nix file.

I wondered if it was something about electron, so I tried installing obsidian too, but i had no issues with it.

Reproduce the Bug

1. install nixos
2. add logseq to your configuarionts.nix file and rebuild
3. start typing

Expected Behavior

No response

Screenshots

No response

Desktop Platform Information

OS: NixOS 22.05 (Quokka) x86_64

Mobile Platform Information

No response

Additional Context

No response

[TBS1996]

update: reinstalled nixos again and now its smoothly, main difference is now its on an SSD rather than HDD.. but even on a harddrive i dont see why it should be slow, slower than obsidian which uses same technology

[cnrpman]

@TBS1996 Logseq is an outliner. It is not actually the same tech as a text editor.
Maybe you can upload a performance profile so we can have a deeper look into the bottle neck of your case:
https://help.figma.com/hc/en-us/articles/360041468414-Record-a-Chrome-Performance-Profile

Or it's related to #4175 , I think it's still an electron issue and we are planning on an update of the electron version #6032

[github-actions]

Hi There! 👋

We haven't seen any activity on this issue in a while 😴, and we just wanted to make sure that it's still relevant. If you're still experiencing this issue, you might find it helpful to update to the latest version of Logseq. The latest version includes bug fixes and new features that may help to resolve this issue, and you can download it from our website. If updating to the latest version doesn't help, please let us know by adding a comment 💬. We're here to help!

If the issue has been resolved or is no longer relevant, that's great news! 🎉
We'll go ahead and close this issue to keep our backlog organized. Please note that this issue will be closed automatically in 20 days if there is no further activity. If you need more time to resolve the issue or provide more information, please just let us know by adding a comment.

Access additional Logseq 🚀 resources:

• Forum: https://discuss.logseq.com
• Blog: https://blog.logseq.com
• Docs: https://docs.logseq.com

Thanks for your contributions to Logseq! If you have any other issues or feature requests, please don't hesitate to let us know. We always welcome pull requests too!