FreeTube icon indicating copy to clipboard operation
FreeTube copied to clipboard

[Bug]: App UI burns in when idle

Open Android789515 opened this issue 1 year ago • 4 comments

Guidelines

  • [X] I have encountered this bug in the latest release of FreeTube.
  • [X] I have encountered this bug in the official downloads of FreeTube.
  • [X] I have searched the issue tracker for open and closed issues that are similar to the bug report I want to file, without success.
  • [X] I have searched the documentation for information that matches the description of the bug I want to file, without success.
  • [X] This issue contains only one bug.

Describe the bug

Unsure how reproducible this is.

Essentially, I have two windows open, one of them has an eight hour ambience video playing and the other has videos I am watching. The latter will "burn in" the UI as soon as I stop interacting with it, meaning that it takes 1-2 seconds for what I do such as scrolling or clicking to take effect. After I initiate interaction and the UI updates it will update real time until I stop and it will burn in again.

Expected Behavior

App is responsive.

Issue Labels

inconsistent behavior

FreeTube Version

v0.21.3 Beta

Operating System Version

Pop Cosmic Epoch 24.04LTS

Installation Method

.deb

Primary API used

Local API

Last Known Working FreeTube Version (If Any)

v0.21.3 Beta

Additional Information

No response

Nightly Build

Android789515 avatar Aug 31 '24 20:08 Android789515

Is your device and your OS able to handle multiple videos playing on YouTube in your web browser? because it sounds to me almost like your device is struggling to play two videos at once so it's only playing one at a time.

absidue avatar Aug 31 '24 20:08 absidue

It's playing them both. It's the UI that is is unresponsive. Could be an OS update that started this.

Android789515 avatar Aug 31 '24 21:08 Android789515

I found out, it's when I have more than one window open and one of them is minimized, that I get the UI freeze.

Android789515 avatar Sep 07 '24 19:09 Android789515

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Oct 08 '24 01:10 github-actions[bot]

I found out, it's when I have more than one window open and one of them is minimized, that I get the UI freeze.

Is this still an issue for you in v0.22.0?

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

github-actions[bot] avatar Oct 29 '24 00:10 github-actions[bot]

I apologize for the late response. Yes, it is still happening for me. If I have two windows open and one is minimized then the open window will burn in the UI and act frozen after I interact such as scroll or click.

I am on PopOS Cosmic Epoch using window tiling.

Android789515 avatar Nov 19 '24 23:11 Android789515

This issue is stale because it has been open 28 days with no activity. Remove stale label or comment or this will be closed in 7 days.

github-actions[bot] avatar Jan 03 '25 01:01 github-actions[bot]

Any update on this?

Android789515 avatar Jan 03 '25 22:01 Android789515

Can you please try without window tiling and see if it works properly? The thought process being that there is at least one other open issue that only happens on tiling window managers (keyboard shortcuts going to the wrong window), so it entirely possible that this is another one of those (maybe your tiling window manager and FreeTube don't agree on which window is the active one, so it stops updating the UI for a window that it thinks is inactive but it's actually the one your window manager thinks is active).

absidue avatar Jan 03 '25 22:01 absidue

This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. Please reach out if you have or find the answers we need so that we can investigate further.

github-actions[bot] avatar Jan 31 '25 00:01 github-actions[bot]

I appologize for the late reply. I turned tiling off and I still have the issue. In fact, I only have to minimize one window and wait a few seconds for the other window to freeze.

Android789515 avatar Feb 01 '25 22:02 Android789515

What version are you using?

What version are you using?

It seems like the issue is gone in the latest version. I saw the update today.

Android789515 avatar Feb 02 '25 02:02 Android789515

The issue is back it seems. I'm currently on the latest version.

Android789515 avatar Feb 03 '25 02:02 Android789515

Maybe i just dont fully understand what you mean with burn in. Try explaining it a different way or provide a video with a description

Video upload limit is 10MB, I don't see how I will be able to provide that.

Android789515 avatar Feb 07 '25 02:02 Android789515

You have tools to compress your video. Try to use a search engine.

Here is the video in the lowest quality I could get it to.

I first show that I have multiple windows open. Then minimize one and wait for the UI to freeze and try to scroll.

Then I show that clicks also are delayed due to the frozen UI. I then show how continuing to interact with the UI to keep it from idling will keep it responsive. Then I let it freeze and show clicks again.

https://github.com/user-attachments/assets/6cd31ef5-11fd-42f5-8df4-b240b0dfbb32

Android789515 avatar Feb 11 '25 23:02 Android789515

Could be an OS update that started this.

why did you mention this? Did it work before the update?

Also did the app always behaved like this or is this "new" behavior?

Could be an OS update that started this.

why did you mention this? Did it work before the update?

Also did the app always behaved like this or is this "new" behavior?

I think it was because it didn't used to behave like this. I just built a new computer and it doesn't seem to have this issue. Could be a Wayland thing since my old PC had an Nvidia card.

Android789515 avatar Mar 02 '25 00:03 Android789515