#4

Also, first and foremost? does this happen with default css and no third party plugins?

#5

I use obsidianite theme and no third-party plugins. I have 1 vault which the app opens into by default. It is 103 items, totalling 2.4 MB. I just turned off obsidianite and am using the default theme and still have the same issues. Even navigating the dev panel is slow. I recorded the performance profile. How/ where would you like me to send it?

#6

you can zip it and upload it here, on dropbox/gdrive and send me the link or you can dm it to me on discord.

#7

Did you use appimage, snap or what?
can you also send a zipped ~/.config/Obsidian/cache ?

#8

What’s your discord username/number?

#9

WhiteNoise#2247

#10

Can report no issues using both Linux Mint and Manjaro KDE. No slowness at all in a vault with ~800 files.
Must be something in the setup slowing you down. Hope you’re able to find it!

#11

Are you using AppImage, Snap, or Flatpak?

#12

I’m sure you’re asking OP, but for me, I avoid snap at all costs (don’t even have it installed on my main rig - a lot of *nix systems don’t even include it anymore). Even a cursory search will show it’s buggy at best.
Appimage all the way - it’s been nothing but stable for me. For most programs I’ve used, including Obsidian. And it’s dead simple to install.

#13

Ubuntu 20.10 flavors replaced the package manager with basically snap manager.

#14

@Erisred I use AppImage in Linux and never experienced slowness with one Obsidian instance open.

is your Linux file I.O still fast?

#15

@ThatOrchid there is a lot of information that is useful to us in the template! Could you please let us know the following:

  • which Obsidian version you have?
  • which installer version?
  • What installation method did you use (AppImage, Snap, Flatpak, or other of the supported ones)?
  • What OS are you on?
#16

This happened to me on Windows when I activated a cursor feature to make it fancy.

#17

I’m on linux manjaro XFCE and have never had any slow performance either.

I use obsidian through an AUR install which is technically the same as the .AppImage, I’ve also tried Flatpack and Snap and none seems to have slow performance issues.

#18

This is not a broad issue. It’s something that this user is expiriencing and we are trying to figure out why.

#19

I believe you mean to direct this to @ThatOrchid - I’ve had no issues on my end - with the OS in general, nor with Obsidian.
Thanks for asking, though!

#20

I have a similar problem.

I am running Debian 10 “Buster”, and I have tried both with Flatpak, Appimage and through .deb installers, same result. I can install and run the package just fine, but when I open it, I get an almost entirely unresponsive window.

However, this only happens when I open it in an X11-based window manager, as is my daily work environment (AwesomeWM). I tried logging in to Gnome on Wayland, and Obsidian ran smooth as a hot knife in butter.
To check whether it was an Awesome problem rather than an X problem, I logged in to Gnome on X, and tried to run Obsidian - which was unusable. So I am pretty sure that at least for me, it’s an X vs. Wayland issue.

I am wondering if there is some GPU rendering issue or something that does this?

#21

I had the same problem. I use Appimage Obsidian 0.10.6 in mxlinux 19.2 using debian 10 buster as a base.

While I used the Googlechrome browser, I started the obsidian (appImage) and changed the themes, then it suddenly slowed down to a halt and no response. I see this could be a problem of the electron base or whatever. Then I closed it from the panel icon, and then restarted it, it seems ok.
Could this be due to themes? what if I had choosed the troublesome theme, then how do I reset it back to the default? Is this theme changing or other than default theme caused problem while changing? I don’t know.

I plan to install it thru snap package instead of appImage, then it asked me to install in user mode or system mode? I am planning to install as a system snap application, so it may have access all over them system.

Now it seems ok. I am not going to change the theme 80_neon which is selected by me. If the problem comes, I will raise it.

#22

Thank you everybody for the datapoints.
I also think that this is not an obsidian internal problem but something external at electron/os level.

I am not convinced that this a broad X11 issue because X11 is quite popular and we would have many more reports.
Perhaps it’s problem with specific GPU drivers and this should happen in other electron apps.

You can try to start obsidian w/o gpu accelleration with --disable-gpu

#23

Which Window Manager or DE are you using? And which display manager? As I wrote above, the problem shows when I use X Windows based environments, but everything is fine in Gnome on Wayland. Have you tried experimenting with this?