Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
M
mutter
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 765
    • Issues 765
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 92
    • Merge Requests 92
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GNOME
  • mutter
  • Issues
  • #850

Closed
Open
Opened Oct 08, 2019 by Christian Hergert@chergertDeveloper

reduced FPS when windows placed behind maximized window

First off, I found this while testing a GTK4 port of GtkSourceView and testing performance on HiDPI.

I notice that the FPS of GTK can drop with a maximized window depending on if there are windows beneath the foreground window. Normally, I would expect this case when shadows are being drawn (since it has to expose the windows behind the foreground). But when the window is maximized, all other draws should be able to be culled.

When I move the maximized window to an empty workspace, the framerate increases.

My expectation would be for these to have the same performance since the other windows are fully obscured.

Edited Oct 08, 2019 by Christian Hergert
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/mutter#850