Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,781
    • Issues 1,781
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 69
    • Merge Requests 69
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #3995

Closed
Open
Opened Oct 26, 2006 by Kitware Robot@kwrobotOwner

glReadPixels on X11 sometimes returns wrong pixels

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


So I tracked down the reason why I didn't turn image caching on in the QVTKWidget yet.

glReadPixels() is returning the wrong pixel data.

glXSwapBuffers() is called, then the next gl/glx call is glReadPixels(). Apparently, glXSwapBuffers() doesn't really happen in time for glReadPixels() to be called (client/server X11 involved).

If I add a call to glXWaitX() or glXWaitGL() before the call to glReadPixels() I get the correct pixel data.

I'm not sure where the right place is to make this gl/glx synchronization happen.

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: paraview/paraview#3995