Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 833
    • Issues 833
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 241
    • Merge requests 241
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTKVTK
  • VTKVTK
  • Issues
  • #15751
Closed
Open
Issue created Sep 30, 2015 by Kitware Robot@kwrobotOwner

vtkOpenGLGlyph3DMapper (OpenGL2 version in VTK 6.3) crash

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


If a glyph indexing is set up, but, for some reason, the input data set does not contain the index array, vtkOpenGLGlyph3DMapper::RebuildStructures only initializes the first cell in numPointsPerSource, leading to a crash during entry->PickIds.resize(numPointsPerSource[cc]) with cc > 0.

I believe all values in the numPointsPerSource array should be initialised to 0 in any case. BTW, why not use a vector instead of this unsafe array? The constructor would take care of the initialisation to 0, and there would be no need for explicit deletion.

Assignee
Assign to
Time tracking