rnote
rnote copied to clipboard
flxzt
Lag
Hey I started using RNote for doing past papers, and its doing a pretty good job, except after a while there is lag and it takes at least 5 second sfor the ink to start working again, its quite irritating especially when you're solving maths or something similar, as you tend to write fast, and without breaks. I want to know how I can fix this, is this happening because of a large pdf size?
Great app tho, thanks a lot for the service!
can you please provide all information requested in the bug report template? Thank you.
Yes I apologise, i assumed this wont be termed as a bug.
Describe the bug
Randomly after a few writings, app appears to lag, and have to wait at least 5-7 seconds before being to enter more writings.
Console Output
I'm not too sure what exactly I should input, I apologise again.
Desktop (please complete the following information):
- OS: Windows 11
- App Version: Rnote v0.10.2
- Installation Source: Installed through .exe file
- Input Source: External Graphics tablet - Huion
Additional context
Lag doesn't immediately start after app is opened and writing is input, it starts about 2-3 mins after writing is started.
I hope this is sufficient.
Just an update, this is occuring for normal documents as well, as in ones with blank pages, and I wrote on them.
Can I ask what hardware you're running rnote on ? I've noticed rnote pen input can sometimes lag when using it after waking a windows device from sleep.
Also lag is much more noticeable on device with a cpu that's more limited as rnote is not currently fully gpu accelerated (so there is some cpu usage, maybe showing cpu usage would be useful to debug this).
I'm also experiencing this on Arch Linux, Intel Alder Lake graphics.
GTK 4.15, GSK_RENDERER={gl,ngl,vulkan} does not affect the laggy situation.
When scrolling with touchpad in a new document, it barely reaches 50 frames per second:
I also experience bad lag on Arch Linux. High CPU usage occurs on only a single core (it doesn't utilize all my CPU cores) after I open the application for about 1 or 2 minutes, then it smooths out. This happens every time I open the application. The thing is, I didn't have this problem on the same hardware in June when I last used the software. It happens with both flatpak and the distro package. I would love to use the application, but cannot because of this issue.
I also experience bad lag on Arch Linux. High CPU usage occurs on only a single core (it doesn't utilize all my CPU cores) after I open the application for about 1 or 2 minutes, then it smooths out. This happens every time I open the application. The thing is, I didn't have this problem on the same hardware in June when I last used the software. It happens with both flatpak and the distro package. I would love to use the application, but cannot because of this issue.
@Amirmohammadomidi Does this happen on 0.10.2 ? Given the timing it might be a specific commit between 0.10.2 and 0.11. You'll have to launch with an additional GSK_RENDERER=gl rnote or GSK_RENDERER=gl flatpak ... for it to work though.
I also experience bad lag on Arch Linux. High CPU usage occurs on only a single core (it doesn't utilize all my CPU cores) after I open the application for about 1 or 2 minutes, then it smooths out. This happens every time I open the application. The thing is, I didn't have this problem on the same hardware in June when I last used the software. It happens with both flatpak and the distro package. I would love to use the application, but cannot because of this issue.
@Amirmohammadomidi Does this happen on 0.10.2 ? Given the timing it might be a specific commit between 0.10.2 and 0.11. You'll have to launch with an additional
GSK_RENDERER=gl rnoteorGSK_RENDERER=gl flatpak ...for it to work though.
Unfortunately, setting these options didn't help. The thing is, I have tested it on a fresh installation of Arch on the same hardware. The even more frustrating thing is that it happens every time I open the app for about 1 to 2 minutes, and then it somehow smooths out. I have monitored the resource usage, and for the first 1 or 2 minutes of opening the app, on a multicore CPU, only one core is utilized 100%.