Skip to content

GitLab

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

Closed
Open
Opened Aug 28, 2018 by Marius Vlad@marius.vlad0Reporter

wet_output_handle_destroy failes with assert when disconnecting an output that has a surface/client rendering on that output

wet_output_handle_destroy is being called when the output is being destroyed. It gets passed a wl_listener and a weston_output. There's an assert that tests if that weston_output is the same as wet_output->output. It seems that wet_output->output points to some garbage memory location upon looking at backtrace. Besides the weston_output, struct wet_ouput members seem to point to correct data. That wet_output->output will only get corrupted if there's an active client when (manually) disconnecting the output.

Edited Aug 28, 2018 by Marius Vlad
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: wayland/weston#136