-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multi-Second Incremental Input Lag in Information Fields #1788
Comments
Thanks for reporting this issue! I have yet to figure out what the root cause is. It's as if something is written to disk synchronously. |
Also experiencing this in the Plot and Outline fields by the way. Tried What I do notice is this whenever this happens:
This was selecting 3 characters, then hitting delete. There are also hundreds of |
Hi all, I'm back from my vacation and tried looking into this issue. I was able to reproduce it using the AppImage only. It's really strange. I have no idea why the AppImage is as slow as it is. The CPU spikes up to 100% while typing. Even if I extract the binary from the AppImage and then start it, the issue persists. The only workaround at the moment is to build MediaElch yourself. Regards, |
What's even stranger: if I try to start the binary using gdb, everything works as expected. |
I'm having this issue using EDIT: So far, compiling it via the AUR is working smoother. I'll leave this instance open and see if the performance degrades as I continue to work on my library. EDIT 2: A full day later with the same MediaElch instance open and actively using it and it's still just as snappy all around. Compiling locally seems to have fixed it. I don't know if this helps at all. I'll post again if it starts acting up. |
So, sometimes I'm finding the AppImage works fine now (same version), particularly if I open it for the first time in a few days (first startup after a reboot, perhaps?); there's still some delay, but a mere quarter second at most, so certainly manageable. This has happened twice: the first time, I closed and reopened it to find the new version had the lag again, and today I decided to open a second instance at the same time and found that version also lagging, with the original instance remaining fine. Journalctl doesn't appear to say anything. Feels like a library/dependency issue of some kind, but not sure. It's a stretch, but possibly related?: AppImage/AppImageKit#1351 |
I'm on X11 KDE and getting this so it's not Wayland related. |
I'm on AwesomeWM (X11). I thought I had said that in my above post but apparently I neglected to. |
Just to follow up, a freeze happened the first time I opened it after rebooting, so bootup alone isn't the sole factor |
I tried different older "linuxdeployqt" versions, but was not successfull. However, v2.10.0 worked fine. I'll try to figure out the commit that made it so slow. |
Seems to be 516c8a5 516c8a5#diff-f2c7c599ccef7d34ec5477a9109f459dd0cfb02423120386e305b307fb8c997eL52 auto movieIndex = qsizetype_to_int(m_movies.indexOf(movie));
Ah, no. It was a linear search before as well... I'm working on a fix. |
I think to have fixed it with #1803 New nightly versions will be available shortly. It would be great, if you could test them. |
Started the latest AppImage up a couple ways and it works perfectly for me; even the quarter-second delay I'd get when the previous one was at its best is gone, as is the 2s delay when selecting images. Thanks for the fix! |
Thanks for confirming! |
Works for me as well 👍 |
Describe the bug
When editing information on a scraped movie, the "Information" and "Streamdetails" sections experience a dramatic slowdown, taking around 2 seconds per character, during which the app cannot be visually interacted with (one can click other fields, edit them, and click other movies, but this does not reflect visually until the writing is finished.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The text field's contents would update more or less in real time to my typing.
MediaElch Version:
Operating System:
Additional context
The text was updated successfully, but these errors were encountered: