Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,874
    • Issues 2,874
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 899
    • Merge requests 899
  • 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
  • Mesa
  • mesamesa
  • Issues
  • #874

Closed
Open
Created Sep 18, 2019 by Bugzilla Migration User@bugzilla-migration

OSMesaMakeCurrent not properly changing contexts

Submitted by James Burns

Assigned to mes..@..op.org

Link to original bug (#11161)

Description

Tracked this down to the check_compatible method in context.c. The depth bits comparison is failing as the OSMesa context creation is using a default of 31 bits for depth. The framebuffer/renderbuffer that is being compared against the context is made with 32 bits, and apparently can not be made with 31 bits (reference renderbuffer.c).

I was able to bypass the depth bit comparison in check_compatible and all works. I am not positive what effect removal of this comparison might have in the bigger scheme, so someone may want to look at this bypass or changing of the OSMESA default depth buffer size.

Version: 6.5

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