Any delay in the compositor thread tends to create the same effect. The spawn_command_line_sync it is slow enough to slowdown the compositor thread and it cause a stuttering. Then open a video in firefox and you will see the video stutter. That “something” is the point of my comment.Įdit2: To reproduce the reporter issue, just create an extension that execute an spawn command line in sync mode every 1 seconds (for example). So, it’s not just the problem of bug 784055, something different to Unity is happening to the issue reporter in gnome-shell. On a 4k monitor, firefox playing 4k youtube video stutters… whereas in Unity it is smooth. ![]() Thanks for sharing all the shell progress and your own work on this.Įdit: In the title of bug 1879604 it said: I’m pretty sure at less a video stutter should not occurs in that way. Isn’t it a good idea to finish fixing the shell architecture at once? i.e.: I think all GUI process should be moved outside the compositor thread. I know I am repetitive, but it is repetitive to see how the 3rd parties apps are blamed for the bad architecture of the shell. But a video stutter should not happens if the indicator-multiload will be running outside the compositor. ![]() ![]() The video stutter is because of the indicator-multiload or this is because the server side of the indicator-multiload is running inside the compositor thread? It’s true that the indicator-multiload is heavy and is also true the Ubuntu implementation of the indicator is really questionable right now as this is happening for all images that AppIndicator receive in the gjs side ( ).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |