Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • W weston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 360
    • Issues 360
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 123
    • Merge requests 123
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waylandwayland
  • weston
  • Issues
  • #436
Closed
Open
Issue created Sep 17, 2020 by John Good@archiesixContributor

Weston crashes on compositor wake up

Sometimes, waking up a sleeping compositor causes a crash. The crash is caused by the assert assert(output->repaint_status == REPAINT_AWAITING_COMPLETION) in the function weston_output_finish_frame of libweston/compositor.c. Steps to reproduce: set a small idle time in weston.ini (i.e., idle-time=3), wait for the compositor to sleep, move the pointer to awake the compositor and repeat until the compositor crashes.

Edited Sep 17, 2020 by John Good
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking