Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
gnome-calendar
gnome-calendar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 413
    • Issues 413
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 25
    • Merge Requests 25
  • 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
  • gnome-calendargnome-calendar
  • Issues
  • #195

Closed
Open
Opened Nov 24, 2017 by Georges Basile Stavracas Neto@feaneronMaintainer

CPU eaten alive as countless sizing operations occur (Allocating size to GcalEventWidget without calling gtk_widget_get_preferred_width/height() )

The git version eats 50% of my CPU through Xorg. While running, thousands of occurrences of this message (with the "0x41387a0" part changing) happen continously:

(gnome-calendar:4973): Gtk-WARNING **: Allocating size to GcalEventWidget 0x41387a0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate?

Link to original bug (#788812)

Design Tasks

TODO

Development Tasks

TODO

QA Tasks

TODO

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: GNOME/gnome-calendar#195