High I/O by vsedit.config.lock

[pZa]

I get max disk i/o (queing?) by the file ~/.config/vsedit.config.lock that hammers (created/deleted) every time i move the main window. It can be seen with iotop for example. Or if you have a mechanical HDD you can clearly hear it. The head seeking is in sync with the mouse/window movement.

I can workaround it by soft linking the file to tmpfs. Unfortunately, it only works if the program is already running. Trying to start it with link already in place freezes vsedit thus i'm here. I think you're maybe opening the file in direct-io/sync mode or something like this. It might stress HDDs/SSDs a lot and probably is not all too healthy for them.

I have one other program (meld - comparison tool) that does the same with ~/.config/dconf.

Arch Linux / XFCE / Xorg

[Aleksey Lyashin]

Seems to be an underlying implementation of something. When you move the main window, the editor saves it position in config to restore it on the next start. It does not intentionally create the lock file. Either Qt or Linux itself does it. You're not supposed to move the main window around that much though. Anyway, nothing I can do about it.

[Aleksey Lyashin]

Qt or Linux behavior. Can't be fixed in this project.

[pZa]

1) The lock file is not the problem. Its the function that saves the settings for every moved pixel. It should rather save the settings when the windows gets dropped/released or when the application gets closed.

2) Can you at least confirm the bug? Does it produce the same high i/o on your system with iotop? If its just on my side i will pass it on to the Arch or upstream maintainers.

[Aleksey Lyashin]

For two years of active development I haven't had such problem in Windows or Linux Mint. Sounds like your problem is that move event occurs at each pixel the window moves. I might come up with a workaround for this problem.

[pZa]

Here is an strace snippet: https://bbs.archlinux.org/viewtopic.php?pid=1799829#p1799829 Edit: And a possible fix.

[Aleksey Lyashin]

Already working on a fix. Turns out the problem actually existed in Mint.