Open justjanne opened 1 year ago
I wrote a small script I ran in the devtools of element desktop to test this:
let run = true;
let lastFrame = null;
const f = () => {
const currentFrame = Date.now();
if (lastFrame) {
console.log(currentFrame - lastFrame);
}
lastFrame = currentFrame;
if (run) {
window.requestAnimationFrame(f);
}
};
window.requestAnimationFrame(f);
It reported this on the primary monitor:
[16, 17, 16, 17, 16, 18, 16, 17, 16, 17, 17, 16, 17, 17, 16, 17, 16, 17, 17, 17, 16, 17, 17, 16, 17, 17, 17, 16, 17, 16, 18, 15, 17, 17, 17, 16, 17, 17, 17]
And this on the secondary monitor:
[983, 1, 998, 1, 999, 1, 16, 984, 1, 16, 983, 1, 16, 983, 1, 17, 983, 1, 16, 983, 1, 17, 983, 1, 16, 983]
@justjanne Anything obviously taking up the time if you record a session in the devtools performance profiler? Can you share the profile file for others to examine?
@justjanne Anything obviously taking up the time if you record a session in the devtools performance profiler? Can you share the profile file for others to examine?
I'll do so tomorrow, but I doubt that's the issue, as just moving it to the other screen makes it run well again.
I think something's wrong with electron, but I haven't yet figured out what specifically is broken.
Steps to reproduce
Outcome
What did you expect?
Element Desktop should be just as fluid as on the secondary monitor as other apps (e.g., Quassel) are, or as Element Web in Firefox is.
What happened instead?
Element was hanging, stuttering, even taking minutes to act on user input. Only electron apps like Element or Discord are affected, it does not affect Quassel or Telegram. It does not occur in element in Chromium or Firefox, only the desktop app.
Operating system
Ubuntu Budgie 22.04.2 LTS
Application version
Element version: 1.11.24 Olm version: 3.2.12
How did you install the app?
Element DEB repo
Homeserver
matrix.org
Will you send logs?
Yes