Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • W weston
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 317
    • Issues 317
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 119
    • Merge requests 119
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • wayland
  • weston
  • Issues
  • #62
Closed
Open
Created Dec 29, 2014 by Bugzilla Migration User@bugzilla-migration

Dangling pointers and memory corruption after output recreate.

Submitted by Andriy Prystupa

Assigned to Wayland bug list

Link to original bug (#87824)

Description

Way to reproduce:

  • weston backend closes current output and creates new one.
  • old weston_output structure is released.
  • compositor views have pointers to old weston_output.
  • these pointers became dangling.

Fix: in weston_compositor_remove_output(...) add resetting reference to output: wl_list_for_each(view, &compositor->view_list, link) { if (view->output == remove_output) { view->output = NULL; view->surface->output = NULL; } }

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking